Who we are and why we're here.

Epieme makes public patient-safety policy records searchable, source-linked, and visible before the hearing, vote, or comment period is already over.

Johns Hopkins campus walkway with people moving through the space.

Partners

Epieme is supported by university innovation partners who help move civic health technology from idea to real-world deployment.

JHU Pava Center

Johns Hopkins University

The Roux Institute

at Northeastern University

Founder's patient-safety work featured in

How it started

Patient safety was never an abstraction in Samson's house. His mom is a pediatric ICU doctor, the person families trust on the worst day of their lives.

Then he watched the system fail her up close.

She raised concerns about safety at the Maine hospital where she worked, and not long after, she was forced out. Samson was fifteen. He wrote a petition about what happened. The hospital's answer was to threaten her with a defamation suit and claim she had written it for him.

So he went looking for the record that proved what they already knew. It was all there, just scattered to pieces. Incident reports in one database, safety ratings in another, the petition on Change.org, the legislative fight buried in committee calendars, and the coverage spread across a dozen news sites that each told one slice of it.

Every time, the deadline moved faster than he could assemble the picture. A hearing would pass. A comment window would close. By the time the story was clear, the chance to act was usually gone.

He did that search by hand, over and over, because nothing existed to do it for him. The petition reached 22,000 signatures. FIRE took up the case. Maine passed LD 870, its anti-SLAPP law, partly because of what his family went through. The fight got won. The system that made it so hard to fight was still standing.

So he built the tool he had needed at seventeen. Epieme pulls the scattered signals together, incident reports, public records, legislation, local news, and turns them into issues anyone can follow. Every summary links back to its source. Every action window stays in view while there's still time to use it.

Word got out. Advocates, patients, and watchdogs in other states started asking for the same thing. What began as one family's fight to be heard is becoming the platform that helps people across all 50 states catch the warning signs early and act while it still matters.

Founder portrait for the Epieme backstory section.
Public records and documents.
Public record
Hospital corridor.
Patient safety

What we believe.

Our purpose guides everything we build and how we work with partners.

Our Purpose

Make patient-safety records visible while people still have time to act.

Our Vision

A future where safety signals are easy to follow, verify, and share.

Source-linked records 12,856 Signals organized across public sources

Our Mission

Help patients, advocates, and watchdogs connect evidence to action across all 50 states.

Epieme radar interface with source-linked patient-safety records.
Action windows 50 States watched for hearings and deadlines

Proof should be one click away.

Founder

Samson Cournane, solo founder and Johns Hopkins MSE graduate student.

LinkedIn profile

Method

Source provenance, update cadence, and correction paths should be visible before any pilot.

Read methodology

Accessibility

Civic-tech and health-adjacent tools need an explicit accessibility standard.

Accessibility statement

What serious visitors ask first.

Where does Epieme get records?

Public state legislative pages, hearing calendars, source documents, petitions, and related policy records. Each surfaced claim should link back to the underlying source.

Who is the first customer?

Patient-safety advocates and policy teams who need to verify public records quickly. Hospital and institutional pilots should use the same source-first workflow.

Is this medical advice?

No. Epieme tracks public policy and accountability records. It does not provide clinical guidance, diagnosis, or legal advice.