Device inbox
Review imported analyzer results, accept mapped values into patient results, and reject unsafe or duplicated device rows.
What appears in the Device Inbox
Open Devices → Device Inbox in the Branch Panel. The Devices cluster also contains Instrument Management, where authorized staff configure only the analyzers assigned to the active branch. Use Instrument Management to fix identity, test mappings, availability, schedules, maintenance, or connection settings; use Device Inbox to review values received from those analyzers.
The Device Inbox lists analyzer results imported by the branch device gateway. These rows may come from file drops, HL7 messages, or ASTM messages. The inbox is branch-scoped, so staff only see rows imported by devices registered to the active branch.
Use this page before clinical review. It is for deciding whether an imported analyzer row can become a pending patient result, not for final report release.
Main columns
| Column | Meaning |
|---|---|
| Sample | The sample barcode sent by the device. |
| Device | The analyzer or gateway source. |
| Device test | The test code received from the device. |
| Raw value | The value exactly as imported. |
| Mapped test | The Kashef test matched through device mappings. |
| Status | Whether the row is pending, unmatched, accepted, rejected, or blocked. |
Safety statuses
Kashef stores the raw device message before creating review rows, so support can always compare the inbox value with the original analyzer payload. Duplicate messages from the same device are skipped after the first successful import, which keeps the inbox from filling with the same analyzer row.
Unmatched means Kashef could not match the sample barcode or device test code. Fix the sample or device mapping, then review the row again. Quarantined means the file or message could not be safely parsed; do not enter it from the inbox until the raw log has been checked.
Accepting a result
Use Accept when the sample barcode and mapped test are correct. Kashef writes the value into the matching sample result as a pending clinical result. The result still needs the normal review and release workflow before it appears on a patient report.
If the row is unmatched, Kashef keeps it in the inbox and explains that the sample or device test mapping must be fixed first. If a manually approved result already exists, the import is blocked so the analyzer value does not overwrite reviewed clinical work.
Rejecting a result
Use Reject for duplicated rows, unsafe device output, wrong sample identity, or values that the team will enter manually. Add a short reason that another reviewer can understand later.
Rejecting an import does not delete the audit trail. It marks the imported row as rejected and keeps the reason with the device result.
Opening the order
Use Open results after accepting a row to continue through the normal results worksheet. Review abnormal flags, previous values, QC context, and report readiness before release.
Daily review rhythm
Review the Device Inbox at predictable times during the shift instead of waiting until the end of the day. A good rhythm is to check it after each analyzer run, before reviewers start releasing reports, and before closing the technical shift. This keeps imported rows close to the physical samples and instrument output that produced them.
When several rows belong to the same sample, process them together. Confirm the barcode, device name, and mapped test before accepting the first value, then keep the order open while you review the remaining values. If one row looks unsafe, reject only that row with a clear reason and continue reviewing the others normally.
Managers should also watch for patterns. Repeated unmatched rows usually mean a device test code is missing from mappings. Repeated blocked rows may mean staff are approving manual results before analyzer imports arrive. Repeated duplicates often point to a device exporting the same file more than once.
When expected rows are missing
Check that the device is assigned to the active branch, the gateway imported the file or message successfully, and the row was not already accepted or rejected. For file-drop devices, also confirm the source file was moved to the archive folder after import. For HL7 or ASTM devices, confirm the device listener is running and that the raw message appears in device logs.
Escalating recurring device issues
When the same analyzer keeps producing missing, duplicated, or unmatched rows, capture the device name, sample barcode, device test code, import time, and latest raw log entry before asking for support. Those details help the team distinguish a connection issue from a mapping issue or a repeated file from the analyzer.