Skip to main content

The Little Engineer that Could

Building the Core Engine of EDORA

Welcome to the engine room of EDORA, the Event-Driven Operations, Records, and Analytics system that aims to transform how Human and Health Services are managed. Today, we’re unveiling the core engine—a set of foundational workflows and database schemas that breathe life into every interaction, decision, and resolution within EDORA.

Whether you’re a technology enthusiast or someone passionate about impactful systems, this post takes you deep into the design and philosophy of EDORA’s core. By the end, you’ll see how each layer of this system is engineered to revolve around one unifying concept: the "Need."

The "Need": The Universal Connection

At the heart of EDORA lies the "Need"—a concept that transcends mere data to represent the driving purpose of the system. A "Need" encapsulates a client’s requirement—whether for housing, therapy, or financial assistance—and serves as the central hub that connects clients, caseworkers, providers, and specialists.

What sets EDORA apart is its commitment to making the "Need" actionable. To achieve this, we’ve structured it into six core actions, which flow seamlessly from submission to resolution. This workflow not only ensures precision but also guarantees that every "Need" is handled transparently and effectively.

The Workflow: From Submission to Resolution

Every "Need" follows a structured journey, visualized in the UML Use Case Diagram below:


1️⃣ Submission: A "Need" can originate from clients, caseworkers, providers, or even the system itself (through analytical insights). Submissions include initial data like the type, urgency, and description of the "Need."

2️⃣ Validation: The system evaluates eligibility and resource availability, leveraging dynamic rules stored in the EligibilityRules table. Validation ensures the "Need" is legitimate, actionable, and supported by real-world constraints.

3️⃣ Assignment: Once validated, the "Need" is assigned to appropriate entities. The system dynamically connects providers, specialists, and other resources, storing these relationships in the SpecialistAssignments table.

4️⃣ Confirmation: The assigned entity acknowledges their role in addressing the "Need." This step locks in the initial milestones for tracking.

5️⃣ Milestones: Progress is tracked through the Milestones table. Each milestone represents a critical checkpoint, from initial assessments to service delivery.

6️⃣ Resolution: The "Need" reaches completion, and the system updates all stakeholders with final outcomes, logging these details for future analysis.

These six stages are more than just a workflow—they’re the foundation of EDORA’s ability to deliver clarity and accountability at every step.

Building Relationships Within the Core Engine

Relationships are the lifeblood of EDORA’s workflows. From validation to resolution, the system dynamically orchestrates interactions between clients, caseworkers, providers, and specialists.

  • Caseworkers: Facilitate the flow of the "Need," ensuring it remains on track and advocating for clients when necessary.
  • Providers: Manage resources, services, and capacity to fulfill the "Need."
  • Specialists: Execute tasks tied to milestones, bringing expertise to specific stages of the workflow.
  • The System: Acts as the conductor, logging every action, decision, and outcome for transparency and adaptability.

These relationships are represented in the database through tables like Specialists, Providers, and SpecialistAssignments. The ValidationHistory table ensures every decision is logged for review, while ResourceTracking monitors availability in real-time.

Introducing the Database Schema

To power these workflows, we’ve built a flexible and scalable data backbone. Here are the key tables that form EDORA’s core engine:

Needs

Tracks the "Need" as a central entity.

  • NeedID: Unique identifier for each "Need."
  • Type: Category of the "Need" (e.g., Housing, Therapy).
  • Priority: Urgency level (e.g., High, Medium, Low).
  • Status: Current state (e.g., Open, Validated, Fulfilled).
  • EligibilityRules: Criteria required for validation.
  • ResourcesRequired: Specific resources needed (e.g., funding, beds).
  • MilestonesStarted: Indicates if milestones are being tracked.

Example:
A "Need" for emergency housing with high urgency, requiring validation of income eligibility and access to available beds.

ValidationHistory

Tracks validation attempts, ensuring transparency.

  • ValidationID: Unique identifier for each validation attempt.
  • NeedID: References the associated "Need."
  • ValidationTimestamp: When the validation was attempted.
  • ValidationStatus: Outcome (e.g., Passed, Failed).

Example:
Validation ID: 501
Need ID: 101
Timestamp: "2024-12-01 08:30:00"
Status: "Passed"

ResourceTracking

Monitors real-time availability of resources.

  • ResourceID: Unique identifier for the resource record.
  • ProviderID: References the provider.
  • Description: Detailed explanation of the resource.

Example:
Resource ID: 301
Description: "3 beds available in temporary housing."

Specialists

Tracks experts tied to providers.

  • SpecialistID: Unique identifier for the specialist.
  • Specialization: Area of expertise (e.g., Housing, Therapy).

Example:
Specialist ID: 801
Name: "Dr. Jane Smith"
Specialization: "Therapy Services"

Milestones

Defines progress checkpoints for a "Need."

  • MilestoneID: Unique identifier for each milestone.
  • NeedID: References the associated "Need."
  • Status: Current status (e.g., Pending, Completed).

Example:
Milestone ID: 201
Description: "Initial Assessment Completed"
Status: "Completed"

Why This Matters

EDORA is more than just a system—it’s a philosophy. Rooted in the EDORA Maslow Philosophy, the framework reimagines the hierarchy of needs to address the realities of Human and Health Services. By focusing on workflows that adapt to real-world constraints, EDORA ensures that every "Need" is met with precision and purpose.

What’s Next?

This is only the beginning. As we refine milestone tracking and expand the schema to include services and interventions, the system will evolve into a fully interactive platform. If you’re as excited as we are about revolutionizing Human and Health Services, join us in shaping the future of EDORA. 🚀💙

Adding Coal to the Engine - Part Two