MedicalTracking

Eight people. Seven weeks.

Equipment, locations, and service requests in one desktop application.

View the project source

WPI academic team project · Lead Software Developer

Follow a request.

Illustrative walkthrough · No patient data

Equipment

  • Type
  • Clean status
  • Location

Location

  • Destination

Service request

  • Equipment
  • Assignee
  • Priority
  • Status

Start with the equipment.

The equipment model keeps type, location, and clean status together, so a request can refer to a specific item.

  • Type
  • Clean status
  • Location
Explore location →Inspect the code

Give the request a destination.

A location gives the request a concrete destination. The application also includes a hospital-navigation component.

  • Destination
  • Location reference
Explore request →Inspect the code

The request connects the pieces.

A service request links the equipment, destination, assignee, and status in one record.

  • OPEN
  • PENDING
  • CLOSED
  • CANCELLED
Explore persistence →Inspect the code

Keep changes beyond the screen.

The model connects equipment changes to SQL or MongoDB storage and supports a CSV representation. The interface is only one part of the product.

  • SQL
  • MongoDB
  • CSV
Explore equipment →Inspect the code

Based on the project’s Equipment and MedicalEquipmentServiceRequest models.

The team I led.

Eight people, a seven-week deadline, and a working product to deliver.

I led technical design, trained teammates, and reviewed code.

See the team credits

Think beyond the brief.

Our team explored facial-recognition login for a hands-free interaction.

Our team placed in the top 2 of 10 in all seven weekly reliability and functionality reviews.

— Amitai Erfanian, reflecting on the course
Explore the hands-free login concept

The idea was to reduce dependence on typing when a hospital worker’s hands were occupied. Our academic prototype included face-recognition login alongside the equipment workflows.

This was an exploration, not a clinically validated or hospital-deployed authentication system. A real deployment would need security, privacy, accessibility, and workflow validation.

Explore the implementation