This article is part of the Dr. Asad Islam paper series within the Somatic & Physical Literacy corpus, a case-derived research program examining what one documented psychiatric-care experience can reveal about patient rights, medical-record integrity, institutional accountability, and the infrastructures through which contested care becomes visible.
The named case provides the originating evidence and questions; the papers develop distinct intellectual objects from them while preserving the boundary between documented fact, interpretation, and what remains unresolved.
Visit:
OSF project to read the Dr. Asad Islam research papers and project materials
AsadIslamPatientExperience.com to review the documented case
SophyLit Substack to follow the series and case as it develops.
I began with what looked like a research problem:
Who might reasonably care about the questions disclosed by one documented healthcare-accountability case?
The answer expanded quickly.
Legislators. Congressional staff. Regulators. Investigators. Attorneys. Journalists. Psychiatric experts. Pharmacists. Patient-safety researchers. Health-law scholars. EHR specialists. Digital-forensics experts. Civil-rights advocates. Professional associations. Librarians. Archivists. Editors. Nonprofits. Policy organizations.
At first, the growing list looked like evidence that more research remained to be done.
Eventually, the repetition disclosed something else.
The problem was no longer insufficient reach.
The problem was that titles were proliferating faster than functions.
An EHR audit specialist and a digital-forensics examiner may occupy different professions while serving closely related evidentiary functions. A health-policy adviser, congressional oversight counsel, and legislative committee staffer may have different titles while participating in different portions of the same policy-routing architecture. A police investigator and a professional-licensing investigator may both investigate, but under different jurisdiction, authority, evidentiary access, and possible disposition.
If every title remained a separate outreach category, the list could continue expanding without becoming more intelligible.
So I stopped treating the work as a contact list.
I began treating it as an operating system.
When the List Became the Problem
The first structural change was to separate role discovery from actual recipients.
A role ontology preserves the many titles through which potentially relevant work appears:
Digital-Forensics Examiner.
E-Discovery Specialist.
Clinical Documentation Integrity Specialist.
Health-Law Scholar.
Privacy Officer.
Diagnostic-Safety Researcher.
Public-Integrity Investigator.
Medical Librarian.
Those titles remain useful for research because institutions distribute similar functions across different professional vocabularies.
But the ontology asks a different question:
What can this role actually do in relation to the problem?
That question reduces hundreds of plausible titles into a smaller number of functional lanes:
direct enforcement; legislative and governmental oversight; digital evidence; independent clinical review; patient safety; health law and civil rights; institutional compliance; journalism; professional standards; advocacy; academic research; health-information technology; insurance and accreditation; preservation; and public scholarship.
The title remains useful for discovery.
The function determines why the role belongs in the system.
The resulting distinctions are:
possible recipient ≠ appropriate recipient
title ≠ function
contact ≠ intake
intake ≠ review
review ≠ disposition
visibility ≠ actionability
The list became easier to govern once those differences remained visible.
Authority, Expertise, and Amplification Are Not Interchangeable
The next distinction concerned power.
Not everyone who may care about a documented problem can do the same thing with it.
A regulator may possess authority to obtain records or issue a professional disposition.
An investigator may be able to reconstruct facts within a defined jurisdiction.
A forensic expert may identify the technical evidence required to test authorship, timing, alteration, or provenance while possessing no authority to obtain that evidence.
A journalist may investigate and expose a public-interest problem without adjudicating professional misconduct.
A scholar may convert one documented event into a transferable research question without determining what legally occurred.
A librarian may preserve, index, and improve discovery of the resulting work without validating the originating allegation.
A legislator may recognize a repeatable policy defect while having no role in deciding the merits of a private clinical dispute.
These are not stronger and weaker forms of the same participation.
They are different kinds of participation.
The operating system therefore records more than a recipient’s name and title.
It asks:
What authority does this recipient possess?
What jurisdiction applies?
Can this recipient compel evidence?
Can this recipient issue a binding disposition?
Is the function investigative, advisory, scholarly, journalistic, legislative, preservational, or public-facing?
What specific question belongs with this recipient?
What would constitute a legitimate reason for contacting them at all?
A prominent title does not create campaign relevance by itself.
The recipient needs a function.
The Complete Record Is Not the Correct Packet for Every Reader
The research also exposed a second form of overproduction.
A complete evidentiary record may be necessary for preservation.
That does not make the complete record the correct first object for every recipient.
A digital-forensics expert may need a chronology, source inventory, native-file list, bounded set of forensic questions, and description of the audit artifacts being sought.
A diagnostic reviewer may need a diagnostic chronology, lineage table, selected clinical records, limited witness or recording evidence, and specific review questions.
A regulator may need the allegation, jurisdictional basis, evidence index, strongest supporting exhibits, and requested action.
A journalist may initially need a short chronology, several independently testable source conflicts, the status of any official proceedings, and one clearly stated public-interest question.
A legislator may need a concise statement of the repeatable policy defect rather than hundreds of pages concerning the originating case.
The operating system therefore contains separate Materials Bundles.
That changed the governing question from:
Who gets the evidence?
to:
What evidentiary object belongs with this recipient for the function I am asking that recipient to perform?
The difference matters.
More evidence does not automatically produce more visibility.
An evidentiary object can remain technically available while becoming functionally unusable because it arrived at the wrong scale, through the wrong route, or without a defined question.
Poor routing can become another form of invisibility.
Available Route ≠ Presently Activated Route
The next problem was temporal.
Some recipients are appropriate now.
Others become appropriate only if something changes.
An insurance regulator may become relevant if insurer conduct or reliance on disputed information becomes part of the evidence.
An accreditation body may become relevant if an accredited institution and applicable standard are established.
An EHR vendor or certification pathway may become relevant after the specific platform, product, or technical behavior is identified.
A foundation may become relevant after a bounded research object exists with defined aims, deliverables, costs, and evaluation criteria.
A journalist who reasonably declines an unresolved individual allegation may evaluate the same material differently after an official disposition, independent corroboration, native forensic evidence, or a clearly demonstrated policy gap.
Deleting those routes would lose potentially useful future structure.
Activating all of them immediately would collapse possibility into obligation.
So the operating system distinguishes:
available route ≠ presently activated route
and preserves a separate Deferred / Conditional layer.
The route remains visible.
Premature contact does not become necessary merely because the route exists.
This became one of the more important corrections to the original outreach logic.
Maximum reach does not require maximum simultaneous contact.
Sometimes disciplined non-contact is part of governed outreach.
A Governed System Must Know When to Stop
A system capable only of expansion is incomplete.
Every unanswered message can otherwise remain psychologically and administratively open.
Every possible recipient can become another imagined obligation.
Every newly discovered title can reopen a research lane that was already functionally complete.
The operating system therefore allows a route to contain a stop condition.
One follow-up may complete a reasonable attempt.
A formal referral may close one route while activating another.
A final disposition may terminate an adjudicative pathway.
A change in role may make the recipient obsolete.
The absence of a required factual predicate may keep a conditional route inactive.
New evidence may later reactivate something that had appropriately remained deferred.
The system therefore governs more than escalation.
activation
continuation
rerouting
closure
responsible stopping
That distinction matters to the larger Somatic & Physical Literacy project.
Visibility preservation does not require indefinite pursuit.
Preserving a route is not the same as remaining permanently obligated to travel it.
Previously Correct ≠ Presently Correct
Verification required its own layer.
Many of the people most relevant to public-interest outreach occupy unstable institutional positions.
Legislative staff change offices.
Committee assignments change.
Agency leadership changes.
Journalists change beats.
Researchers change institutions.
Programs merge, close, or acquire different responsibilities.
A recipient who was correctly identified during research can become incorrectly described before outreach occurs.
The operating system therefore separates research provenance from current verification.
A live recipient can carry:
a verification date;
a source;
a current-status field;
and an instruction to reverify the role before contact.
That may appear administrative.
It is epistemic.
Previously correct ≠ presently correct.
Research should not silently acquire permanence merely because it has been entered into a spreadsheet.
From Research Reservoir to Governed Outreach
The private operating system currently contains 306 canonical Master Outreach entries.
That number may change.
The number is also not the point.
The useful development is that those entries no longer appear as 306 unrelated people I might someday be obligated to contact.
They now sit inside a sequence:
role discovery
↓
functional mapping
↓
candidate research
↓
canonical recipient
↓
authority classification
↓
specific ask
↓
materials bundle
↓
trigger
↓
outreach
↓
response or referral
↓
disposition
↓
stop condition
The spreadsheet is therefore not merely a place where contacts are stored.
It preserves the relations required for outreach to remain intelligible.
A recipient remains connected to why the person was researched; what function the person serves; what authority the person possesses; what evidence belongs with that function; what request is being made; what must occur before contact; what happened after contact; and when the route should end.
The research reservoir became a routing architecture.
The routing architecture became an operating system.
Why a Public Version May Be Useful
Some of this work should not remain specific to the case that produced it.
A person trying to report institutional wrongdoing, contest a healthcare record, preserve evidence, pursue patient-safety reform, approach a journalist, locate technical expertise, or translate a documented experience into research may not know what kinds of institutional actors exist around the problem.
They may not know the difference between:
an investigator and an oversight counsel;
a professional licensing authority and a professional association;
a health-information governance expert and an EHR forensic examiner;
an adjudicative route and an advisory route;
an archival function and an accountability function.
They may also encounter the same problem I did:
Every new title can look like a new destination when the underlying function is already represented.
For that reason, I created a case-neutral SPL Accountability Outreach Operating System template.
The public workbook contains:
a Role Ontology;
a Master Outreach structure;
a Candidate Reservoir;
Office-Level Routing;
Materials Bundles;
Triggers & Dependencies;
Research Verification;
Deferred / Conditional pathways;
and a formula-driven Priority Dashboard.
The public template contains examples rather than my private recipient intelligence.
It is also important to preserve what the workbook does not establish.
It does not determine that a complaint is valid.
It does not establish jurisdiction merely because an office appears relevant.
It does not guarantee that a recipient will engage.
It does not convert a possible route into an obligation to contact.
It does not replace verification of current roles, procedures, law, policy, or evidentiary requirements.
It is not a directive for indiscriminate mass outreach.
Its purpose is narrower:
to preserve enough structure that a large accountability landscape can remain differentiated while decisions about contact are still being made.
Another Visibility Problem Became Visible
SPL has repeatedly treated visibility as something more demanding than the mere existence of information.
Evidence may exist without becoming usable.
A right may exist without becoming operational.
A workflow may exist without an identifiable institutional bearer.
A record may remain available while the relations required to interpret its chronology disappear.
This work disclosed another version of that problem:
A recipient may exist while the evidence still lacks a route.
Finding someone capable of seeing the material does not by itself establish meaningful visibility.
Routing may also require knowing:
who should receive the object;
which version belongs with that recipient;
why that recipient is institutionally relevant;
what question is being placed before them;
what authority they possess;
what must occur before contact;
what outcome that route could actually produce;
and when further contact is no longer justified.
I began with a list of people.
The list disclosed repeated functions.
The repeated functions required an ontology.
The ontology required routing.
The routing required timing, evidence boundaries, verification, and stopping rules.
The result became an operating system.
The scale did not disappear.
It became governable.
The distinction I am carrying forward is therefore:
visibility ≠ routability
Evidence may be visible and still have nowhere intelligible to go.
For accountability work, preserving visibility may sometimes require preserving the route as carefully as the object being routed.
Public Resource
The accompanying case-neutral workbook is available as:
SPL Accountability Outreach Operating System — Public Template
It contains eleven coordinated sheets for role mapping, recipient research, authority classification, evidence routing, dependencies, verification, deferred pathways, and campaign-status review.
The template is offered as a reusable organizational surface rather than as a prescribed outreach sequence.
Different cases will disclose different jurisdictions, different recipients, different evidence, different limits, and different stopping points.
The purpose is not to determine those answers in advance.
It is to keep the distinctions visible long enough for them to be answered responsibly.
One list can contain many names.
A governed system has to preserve why each one is there.