Know why, not just what.
Your systems hold the approved facility, the settled claim, the filed opinion. dhi holds the reasoning behind them - attributed to the person who gave it, at the time they gave it.
What it does
Three principles distinguish dhi from conventional search and transcription tools.
It keeps what was said, attributed.
Every claim carries who said it, when, in which meeting, about what. Nothing is overwritten - a correction is a new claim linked to the old one, so the institution can see what it used to believe and when that changed.
It keeps disagreement.
When two committees reach different conclusions about the same exposure, both survive. The contradiction is the finding, not a problem to be resolved into a single confident answer.
It surfaces what nobody asked about.
A decision raised in four meetings and never resolved. The same exception granted independently, twice, years apart. Search answers questions. dhi raises them.
How capture works
Meetings on the platforms you already use (Zoom, Microsoft Teams, Google Meet). An ad-hoc recorder for the rooms that never touch a platform - a client’s office, a site visit, the conversation after the committee. Documents and email from your existing repositories, under their existing access controls. A purpose-built device, optional, for rooms where none of the above reaches.
Consent is recorded per source, not assumed. Every captured item carries the basis under which it was captured. An item whose basis has been withdrawn is not processed.
Findings
dhi watches for conditions that are true, consequential, and that nobody has noticed - because noticing them would require someone to be counting.
The same exception, granted independently.
Three instances of the same waiver in twelve months, approved by three different people, none aware of the others. Not an exception any more - undocumented policy.
A decision that stopped moving.
Raised at three sittings across six weeks with no approval, declination or dated deferral recorded. A deferral is not a decision, and a deferral nobody dated is invisible.
A reserve that moved with nothing behind it.
Four revisions across eight months and no assessment, no survey, no document in any interval. Reserves are supposed to move as information arrives. This one moved without any.
A relationship that changed hands and left its reasoning behind.
Coverage transferred, open facilities, no handover recorded.
The boundary
No finding is ever about a person.
Findings describe decisions, cases and processes. A person is not a permitted subject - enforced in the data model, not promised in a contract.
It surfaces. It does not decide.
No score, no rating, no recommendation. There is nothing for your model risk function to validate, because nothing of that kind is produced.
Nothing reaches anyone until you say so.
Every engagement begins in shadow mode. The system runs on your real data. It detects everything it would detect and determines who each finding would have reached - and delivers nothing.
A nominated administrator sees exactly what would have surfaced and to whom. You verify the access model behaved correctly, on your own organisation, on your own material, before a single item reaches a single person.
Name someone who should not see a particular item. Nothing returns - and nothing indicates that anything was withheld.
Name a sensitive item. We show who can see it, derived from your own structure rather than declared by us.
Tell us someone moved department, or that a restriction now applies. Watch access change, and watch which direction it fails in.
Ask who could have seen a given item on a date last quarter.
Decision Reasoning
Preserve why decisions were made, including dissenting opinions and exceptions.
Findings
Conditions that get surfaced without someone needing to search.
dhi Presence Device
Dedicated in-room hardware for rooms that never touch a screen.
Start with one meeting environment in shadow mode
Choose one committee on Teams, Zoom, Meet or in a room. Verify what dhi surfaces before anyone sees an output.