https://github.com/mizcausevic-dev/care-pathway-command-center

Operational command center for care-pathway coordination, handoff risk, and follow-up escalation across patient journeys.
https://github.com/mizcausevic-dev/care-pathway-command-center

care-coordination care-navigation care-operations command-center fastapi healthcare-operations healthtech operational-analytics patient-flow population-health python workflow-orchestration

Last synced: 1 day ago
JSON representation

Operational command center for care-pathway coordination, handoff risk, and follow-up escalation across patient journeys.

• Host: GitHub
• URL: https://github.com/mizcausevic-dev/care-pathway-command-center
• Owner: mizcausevic-dev
• Created: 2026-05-12T19:26:33.000Z (21 days ago)
• Default Branch: main
• Last Pushed: 2026-05-17T05:12:19.000Z (16 days ago)
• Last Synced: 2026-05-17T07:26:13.716Z (16 days ago)
• Topics: care-coordination, care-navigation, care-operations, command-center, fastapi, healthcare-operations, healthtech, operational-analytics, patient-flow, population-health, python, workflow-orchestration
• Language: HTML
• Homepage: https://kineticgain.com/
• Size: 1.48 MB
• Stars: 0
• Watchers: 0
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md

Awesome Lists containing this project

README

          
# Care Pathway Command Center

Operational command center for care-pathway coordination, handoff risk, and follow-up escalation across patient journeys.

## Why it matters

Care operations rarely fail because teams lack data. They fail because handoffs drift, queues hide urgency, and no one owns the next action clearly enough. This repo models a care coordination layer that keeps discharge, referral, follow-up, and outreach work visible under pressure.

## What it does

- Scores active patient pathways by risk, delay pressure, and follow-up friction

- Prioritizes a coordination queue for nurses, navigators, and outreach teams

- Tracks cross-team handoffs with cause, severity, and recommended response

- Publishes human-readable proof surfaces and API-friendly outputs from the same service layer

## Proof

![Overview](screenshots/01-overview.png)

![Queue](screenshots/02-queue.png)

![Handoffs](screenshots/03-handoffs.png)

![API Summary](screenshots/04-api-summary.png)

## Local run

```powershell

cd care-pathway-command-center

py -3.11 -m venv .venv

.\.venv\Scripts\pip.exe install -r requirements.txt

.\.venv\Scripts\python.exe -m app.main

```

Open:

- `http://127.0.0.1:4887/`

- `http://127.0.0.1:4887/queue`

- `http://127.0.0.1:4887/handoffs`

- `http://127.0.0.1:4887/docs`

## Validation

```powershell

.\.venv\Scripts\python.exe -m unittest discover -s tests

.\.venv\Scripts\python.exe scripts\run_demo.py

.\.venv\Scripts\python.exe scripts\smoke_check.py

.\.venv\Scripts\python.exe scripts\render_readme_assets.py

```

## Repo layout

- `app/main.py` FastAPI routes and local runtime entrypoint

- `app/services/care_pathway_service.py` coordination scoring and sample payload logic

- `app/data/sample_pathways.json` sample pathway, handoff, and intervention data

- `app/render.py` README proof surface generation

- `docs/architecture.md` system framing and data flow