Skip to content
Prototype v0.1 · All issue records are demo / synthetic data
Back to the map
OpenTechnologydemo-connect-011Demo / synthetic data

Clinic record system unusable during power cuts

Example district clinic · West Africa (synthetic)

Date observed
27 Feb 2026
Last update
8 Jun 2026
Local contact
Clinic records officer

Current status

  1. Observed

    Completed

  2. Verified

    Completed

  3. Open

    Current

  4. Solution Proposed

    Not reached

  5. Testing

    Not reached

  6. Resolved

    Not reached

  7. Monitored

    Not reached

Active and awaiting workable solutions.

WHAT WOULD CHANGE THIS STATUS?

A documented count of outage hours against records lost, plus one workable offline-first proposal, would move this to Solution Proposed. Evidence that the backup supply already covers the gap would close it.

Every record states in advance what evidence would move it. A status is a current reading of the evidence, not a verdict.

Local context

OBSERVATION

Staff fall back to paper during outages and then re-enter records later, producing duplicates and gaps.

Who is affected: Clinic staff and their patient records (synthetic).

Evidence

Evidence summary: Synthetic duplicate-record counts; under review.

Evidence here does not mean absolute truth. It means: a record exists, with a source, a date and a provenance, and it has reached the review stage shown below.

EVIDENCEConfidence: ModerateUnder review

Counts of duplicate and incomplete records matched against outage dates.

Source
Clinic records officer (synthetic)
Evidence submitted
16 May 2026
Provenance
Internal export; matching against outage dates done manually.
Evidence reviewed
Not reviewed

What is needed

  • Offline-first data design
  • Conflict-resolution logic
  • Staff workflow review
  • Low-power hardware advice

Proposed solutions

No active proposal. This issue is waiting for someone who knows how to approach it.

Tests

No solution proposed yet.

Updates

  1. OBSERVATION· Local contributor

    Duplicate records appear after each outage.

  2. EVIDENCE· Local contributor

    Duplicate counts submitted; matching method noted as manual.

Outcome

No outcome recorded yet. This is the current evidence-backed state of the issue, not a final conclusion.

Offer a solution

A proposed solution is not a verified solution. It enters as Solution Proposed and only testing can move it forward. Local people decide what is workable in their context.

State the assumption your proposal depends on.

If nothing could disprove it, it cannot be tested.