CampusCare Bridge

What it is

CampusCare Bridge is a proposed low-bandwidth student health navigation service. It helps a student move from an uncertain question to a verified next step without pretending to diagnose or replace a clinician.

Example user flow

A student writes, “I need counselling but I do not know where to start.” The service asks for consent and a short urgency check, searches a verified UNISA service directory and approved public guidance, then returns one referral card with the service, hours, access needs, and next step. High-risk signals go to a human review path.

How we would build it

The MVP would use a Python/FastAPI service, a mobile-first web interface, structured referral records, a rules-based safety gate, and retrieval from a versioned guidance library. An LLM would explain approved source material only. FHIR-compatible resources would make future handoffs easier to integrate. An SMS fallback would support low-connectivity users.

Safety and privacy

The service would not diagnose, prescribe, or make clinical decisions. It would use minimal data collection, consent, source ownership and update dates, least-privilege storage, audit logs, synthetic test cases, and red-team testing. Voice and remote-care links would come only after supervised safety and usability review.

Pilot and evaluation

The first pilot would be a supervised sandbox with student services and clinician reviewers. We would measure referral correctness, time to referral, comprehension, safe escalation, low-bandwidth completion, language coverage, and accessibility feedback before any live student use.

Current status

This is an original first-round concept and implementation plan. It does not use patient data and makes no clinical deployment claim.

Built With

• fastapi
• python