INDEPENDENT POLICY & RESEARCHConceptual framework Edition 0.22.0
Trust and oversight

Data sharing, rights and local authority

Identify who may authorize the exchange, what decision needs each data field, how people can challenge it, and how each partner can opt out or end the arrangement.

How it could work

Build a purpose-bound record of approved fields, recipients, retention and review. Test aggregate or de-identified information first where it can answer the operational question. Keep an independent route to report misuse.

Where it can fail

More granular data may improve a narrow operational check while widening exposure and reuse risk. Aggregates can still be sensitive in small groups and different partners may have different obligations.

What to measure

Count data fields with recorded approval and purpose, reports of unauthorized use, unresolved rights requests, corrections, and time to revoke access or revert to local operation.

Design a test

Run a tabletop with a reasonable information request, an out-of-purpose request and withdrawal by one participant. Observe how teams deny, record and review consequential decisions.

When to pause or retest

Withhold rollout if purpose, authority, participation, review, exit or protections for sensitive information are unresolved.

What this evidence can support

General risk guidance can inform design. The brief cannot decide whether a particular flow is legally permitted; that requires the applicable rules and authorized review.

Trace the decision

From a capacity request to a limited information exchange

A facility-level request may be sufficient to coordinate supplies without sharing personal records. Test this against a specific decision, including what happens when a partner refuses or withdraws.

  1. Define the support decision
  2. Approve only the fields needed for that decision
  3. Observe delivery, revocation and local continuity

Log fields requested, permissions granted, timely receipts and any service loss after revocation.

When this overlaps another topic

Minimum service reports can omit personal records

A partner deciding whether to send supplies usually needs a quantity, location, cutoff and request status. Any request for finer detail needs a separate justification and review.

Check: Compare tasks using facility-level reports with tasks that request more fields; record what actually changes and exercise refusal, revocation and review.

Hospital and clinic continuity

A withdrawal plan needs a practical test

A policy could allow participants to decline or withdraw, yet in practice leaving may cut off an essential service or make local records unusable.

Check: Exercise withdrawal by a willing participant, check what records remain locally available, and record whether others can still perform the permitted work.

Civilian cooperation and mutual aid

Independent operation also needs lawful records

A backup can preserve service while undermining purpose or retention limits if it quietly duplicates unnecessary data. Define which fields and records are essential to local decisions.

Check: Simulate a shared service loss and a later withdrawal. Audit local access, expiry, unresolved decisions and whether the shared copy can be reconciled or revoked.

Local fallback and independent operation

Sources and scope

These references support particular methods or historical context. The research design above is a proposal.

Original hypotheses to examine

These source records remain untested.