About InfoNotData

Healthcare needs info, not data.

Health systems don’t lack data. They have 800-page faxes full of it. What they lack is the one fact a specialist needs, found fast, with proof of where it came from. That’s what InfoNotData is for.

01 / Why we exist

We built this for the people doing document archaeology.

Every day, nurses, intake coordinators, and HIM staff scroll through long faxed records looking for a single value: an ECG date, an ejection fraction, a pathology result. The value is usually there. Finding it takes time that should go to patients.

Most software treats this as a storage problem, or hands clinicians a generated summary they then have to check. We think both miss the point. Clinicians need specific facts, and they need to see where each one came from.

So InfoNotData does three things. It decides what each page needs before spending money on it. It extracts only what the intake checklist asks for. And it cites every value to its page and line, sending anything it isn’t sure about to a person.

02 / What we believe

Three principles, in the product and on this site.

Cite it or don’t say it

Every extracted value links to its page and line. On this site, every number carries its source or a “Projected” label.

Know what you don’t know

Uncertain pages go to a person, never a guess. On this site, we say plainly what the product doesn’t do.

Filter before you spend

No expensive model pass on a page that doesn’t need one. Cost and speed come from the design, not from slogans.

03 / The belief we reject

“Generative AI will summarize the chart for you.”

Summaries can hallucinate and hide nuance, and running a model over every raw page wastes time and money. In clinical intake, precision plus an honest “I don’t know” earns more trust than confident guessing.

Read more in extraction vs. generative AI for clinical documents.

04 / Where we are

Based in Tampa, Florida.

InfoNotData is based in Tampa. The problem we work on is close to home: a single Tampa Bay health system receives about 1.8 million faxes a month. More about Tampa Bay.

06 / Next step

See it on a real packet.

A 30-minute walkthrough with an engineer. We’ll run a synthetic or de-identified packet through routing, extraction, and citation, and show you exactly where it hands off to a person.

What happens next

  1. An engineer replies to set a time that works for your team.
  2. A 30-minute walkthrough on a synthetic or de-identified packet.
  3. If it fits, we scope a pilot on your own queue.

An engineer, not a sales script. We’ll show you what it doesn’t do, too.

Tampa, Florida
Where do your faxes land?
Organization type
Pages a month. A rough estimate is fine.
Who should we talk to?
Anything we should prepare?
For example: your specialty, your EHR, or your security review timeline.

Business contact details only. Please don’t include any patient information.