Expanding the Tracks for EDORA
Welcome aboard the EDORA Express!
🚂 After the milestones of “The Little Engineer That Could” and “Feeding the Coal to the Engine,” we’re pulling into the next station—a critical juncture for expanding and perfecting EDORA’s framework before moving full steam ahead into development.
This train stop is about laying the tracks for the next steps, refining our workflows, and preparing the system for the journey ahead. It’s not just about where we’re going—it’s about how we’re getting there.
Upcoming Stops on the EDORA Line
Here’s the itinerary for our next four major steps:
🚉 Step 1: Expanding Workflow Details
We’re diving deeper into EDORA’s engine room to define the finer mechanics of its core workflows. This includes:
- Dynamic Eligibility Rules: A rules engine to evaluate and validate "Needs" against criteria like income thresholds, residency, or service availability.
- Milestone Tracking: Establishing clear checkpoints, both sequential and parallel, to monitor progress for every "Need."
- Resource Management: Refining how resources (like beds, funds, or specialists) are allocated, tracked, and pooled across providers.
These enhancements are vital to ensuring every "Need" flows smoothly through EDORA’s system, no matter the complexity.
🚉 Step 2: Simulating Real-World Scenarios
Once workflows are expanded, it’s time to test their mettle. This step involves:
- Running end-to-end simulations to mimic real-world use cases, from submission to resolution.
- Using test scenarios like emergency housing allocation or therapy scheduling to validate eligibility rules, milestones, and resource management.
Simulations are critical for identifying gaps, refining processes, and ensuring the system is ready for action.
🚉 Step 3: Finalizing Core Logic & Mapping UI/UX
After testing workflows and relationships, we’ll move to the design phase:
- Core Logic: Define RESTful/GraphQL endpoints for workflows like
/submitNeed,/validateNeed, and/trackMilestones. - UI/UX Mapping: Design intuitive navigation paths and data flows for user interfaces, ensuring seamless interaction with the core engine.
This step bridges the back-end and front-end, creating a blueprint for development.
🚉 Step 4: Development & Documentation
The final stop before launching prototypes:
- Build modular components in ReactJS/NextJS, backed by Node.js and TypeScript.
- Finalize technical documentation, including:
- Entity-Relationship Diagrams (ERDs)
- API contracts
- Sequence diagrams for workflows.
This step brings all previous work to life, transforming ideas into tangible, functional systems.
Why We’re Sharing This Journey
Collaboration fuels progress, and we’re inviting the open-source community and stakeholders to join us. We want your insights on:
- Potential edge cases we may have missed.
- How eligibility rules or resource tracking could be more flexible.
- Ideas for building transparent and user-friendly UI/UX components.
EDORA is a framework designed to evolve, and every perspective helps make it stronger.
What I’d Add or Emphasize
- Dependencies Between Steps: Results from Step 1 will directly shape the simulations in Step 2, and these will in turn guide the logic in Step 3.
- Modular Development: Building modular UI components allows flexibility for future adjustments.
- Community Feedback: Fresh perspectives can uncover blind spots and refine edge cases. Share your thoughts!
All Aboard for the Next Stop!
The EDORA Express is gaining momentum, and we couldn’t be more excited to have you along for the ride. With each train stop, we’re getting closer to a system that revolutionizes Human and Health Services. Stay tuned as we expand these tracks and set the foundation for a scalable, adaptable, and impactful future.