[ DIGITAL FORENSICS & EVIDENCE INTEGRITY ]
A record is only evidence if you can show it was not changed.
We build software that produces records a third party can check. The method is the same every time.
ARTIFACT>METADATA>PROVENANCE>INTEGRITY>REPORT
The disciplines
Evidence integrity
Each report is hashed with SHA-256 when it is created. Change one character afterwards and the hash no longer matches.
Metadata
Every record carries what was counted, when it was recorded, and which input produced it: manual entry or camera.
Provenance
Records live in a local ledger with three linked views: medications, inventory and an audit log of events.
Controlled deletion
Deleting a record is a separate, confirmed action that the app can restrict by license level.
Forensic reporting
Reports state the expected count, the physical count, the difference and a plain conclusion, then export as a sealed bundle.
Private handling
We publish methods, not evidence. No case material or personal records appear on this site.
[ IN PRACTICE ]
What an RxAuditor report contains
These field names are taken from the app.
| Field | What it records |
|---|---|
| REPORT IDENTIFIER | A unique identifier for the report |
| TIMESTAMP RECORDED | When the audit was recorded |
| FORENSIC SHA-256 | The SHA-256 hash that seals the report |
| SYSTEM STATUS | The audit conclusion |
Medication Adherence Certificate
For a patient: baseline count, physical count, the difference, and whether the count matches the prescription schedule.
Schedule II Forensic Audit Certificate
For an institution: expected dispense count, enumerated count and the reconciliation result.
[ THIS DISCIPLINE, SHIPPED ]
RxAuditor
Evidence integrity, applied to a medication count.