Traceability
Who reviewed this, and under which professional license?
That is not a question you want to answer by digging through a filing cabinet. Itzli keeps the answer on every result, from the moment the sample comes in to the moment someone picks up the report.
What gets recorded, step by step
Every row is a fact the system records on its own, with nobody having to remember to write it down.
| When | What the system records |
|---|---|
| The order comes in | Who entered it, at which branch, which tests and at what price. Plus the patient’s consent, with the version of the text they accepted that day. |
| The sample is collected | The container each test calls for, printed on the label with its barcode, so nobody has to guess the tube. |
| The result lands | If it came from an analyzer, which instrument and at what time; if it was entered by hand, who typed it. Plus the reagent lot that was open at that moment. |
| It is reviewed | Who reviewed it, when, and the reference range applied for the patient’s age and sex. |
| It is released | The signer’s name and professional license number, frozen exactly as they stood that day. If that person’s details change later, the old report keeps the ones it had. |
| It is delivered | Who received the report, how they are related to the patient, the channel it went out through, and the consent it went out under. |
| It is corrected | If a result already released is corrected, the full history stays: what it said before, what it says now, who changed it and why. |
The license number is not a text field
In Itzli, holding the “review” permission is not enough. To review or release a result, the user needs their professional license number verified on their credential inside the system. Without it, the button is not there.
It is deliberately inconvenient. A role permission gets handed to someone by accident; a verified license does not.
Sanitary officers of record
Who answers for each branch before the health authority, with their license number and its validity dates, recorded in the system instead of a filing cabinet. The regulation behind it is NOM-007-SSA3-2011 (Mexico’s standard for clinical laboratories), section 5.1.6.
Four ways to sign
A scanned handwritten signature, one drawn on screen, a digital one, or by recording the e.firma credential (the Mexican tax authority’s digital identity). Each laboratory picks the one it uses, and it is stamped on the report.
Append-only log
Sensitive actions are written down and cannot be deleted or edited afterwards. If it happened, it is still there.
What Itzli does not do, said plainly
In health software, overpromising is not aggressive marketing: it is a legal problem. These are the three things we do get asked about and are not going to say we do.
We do not sign the PDF with an advanced electronic signature
The system records the credential of whoever signs and stamps it on the report. That is not the same thing as a cryptographic advanced electronic signature over the file, and we are not going to call it one. If your laboratory needs an advanced electronic signature in the strict legal sense, Itzli does not give you one today.
We do not certify you and we do not put you in compliance
Certification belongs to the laboratory, not to the software. What Itzli does is record the facts an inspection is going to ask you to demonstrate. You are the one who complies; we just leave you able to prove it.
We are not an electronic health record
Itzli keeps the patient’s tests and their result history. It is not an EMR: no clinical notes, no diagnoses, no progress records. That is a product decision, not a pending item.
How the patient’s data is protected
A lab result is sensitive personal data. The LFPDPPP (Mexico’s federal data protection law) does not treat it the way it treats an email address, and neither does the system.
Encrypted in transit and at rest
The connection runs over TLS and the database is encrypted. On top of that, the fields that identify the patient are stored encrypted field by field.
Versioned consent
It is not enough that the patient agreed at some point: the system stores which version of the text they accepted, and when.
Everyone sees only what is theirs
Permissions are resolved on the server, by laboratory and by role. The receptionist does not see what the lab chemist sees, and neither of them sees another laboratory’s.
Delivery receipt
When a result leaves the laboratory there is a record of who it was handed to and under what authorization — which is exactly what the law expects you to be able to demonstrate.
Minimum five-year retention
In line with the clinical record framework in force in Mexico.
QR verification
The page the QR code opens confirms the report exists and what state it is in, without showing a single clinical value or the patient’s name.
We will show you on a real order
In the demo we open the log of one order and you see every fact recorded: who entered the results, who reviewed them, under which license they were released, and who received them.
- We migrate your catalog, at no cost
- 30-day trial on your real operation
- If your cash drawer does not balance in 60 days, you do not pay