Return to the case study

Supporting evidence

COVID resource database

The complete artifacts and detailed records behind the account. Current public references, original work and proposed designs retain their labels.

Detailed material

Availability changed faster than a static list

During the second COVID wave, resource availability could change while families and field teams were looking for help. A shared list depended on people continuing to supply and communicate updates.

The database contribution

I created a shared database bringing together bed, oxygen and medicine availability. Volunteers and ground staff supplied updates from different locations in India.

The resource was intended to make that information accessible to patients, families and hospital or field teams. Multi-location collaboration does not establish comprehensive national coverage.

People supplying and communicating updates

I contributed to coordination between volunteers and ground staff alongside the database. The work combined a place to find information with people communicating changes.

The historical account does not establish a database schema, automated update mechanism, freshness guarantee or verification protocol. No patient or volunteer personal information is published here.

Contribution

The contribution was a shared bed, oxygen and medicine resource database and volunteer/ground-team information coordination during April–June 2021. No clinical result is attributed to it.

An information service includes its maintainers

The database was one part of the resource. Its usefulness also depended on people continuing to supply and communicate changes. That experience informs how I approach products built on changing operational information.

Notes and sources

  • The March 2022 career record documents the volunteer contribution. Its broad thousands-helped description is self-reported and is not used as a verified beneficiary, referral or clinical-outcome count. The account does not establish the software stack, verification protocol or automated update mechanism.
    Return to the case study