Microbiology - Result corrections (post‑release amendments)

Before release, results can be edited freely. After release, any change must be documented and issued as a corrected result (or addendum per your policy). Corrections update the patient record, regenerate a Corrected report, and trigger re‑distribution to configured destinations.

What counts as a correction

• Changes to values, units, flags, organism IDs, susceptibilities, or interpretive comments after results were released.
• Clerical fixes (e.g., typo in comment) may be handled as an addendum if your policy allows. Otherwise, use a correction.

What happens on correction

• The system captures a full audit trail (who, when, what changed, and why).
• A Corrected report is generated; portals and interfaces (HL7) are updated.
• Downstream recipients are notified according to your Report Rules.

📘 Instructions: Correct a microbiology result

1. Open Result Entry

• Click Microbiology → Result Entry.

2. Search for the order

• Click Search.
• In Order Search, set filters and include Final in the Status filter to find released orders.
• Click Find, select the order(s), then click Done.

3. Load tests for editing

• In the Orders grid (top), select the order.
• The Tests grid (middle) displays linked tests; select the test to correct.
• The Results grid (bottom) shows the result row(s).

4. Edit the result

• Click the Result cell (or relevant fields like units/flags) and make the change.
• Avoid using Mass/Batch entry for corrections to reduce risk of unintended changes.

5. Enter the correction comment (required)

• Click the Comments button at the top.
• In the Final Report Comments tab (it appears contextually based on your selection), document the correction:
  • Reason for change
  • Original value and new value (if applicable)
  • Who was notified and when (for critical/significant changes)
  • Any relevant context (e.g., instrument rerun, specimen issue)

6. Review prior values (optional)

• Click History to see previous results for that test.

7. Save and release the correction

• Click Save.
• If your workflow requires, use Review and Release to finalize the corrected result and trigger re‑distribution.

What to include in a good correction note

• Concise reason: e.g., “Transcription error corrected” or “Updated after repeat run”
• Original vs. corrected value (or comment)
• Notification details for significant/critical changes (name, time, read‑back if applicable)

Best practices

• Never use mass entry for corrections; update rows individually and verify each change.
• For critical corrections, follow your critical value call workflow and document read‑back.
• If multiple components need changes, correct and save incrementally to minimize conflicts.

Compliance, audit, and permissions

• Only authorized users can correct released results; dual sign‑off may be required for certain tests.
• Every change is audit‑logged (user, timestamp, fields changed, comments).
• Corrected reports are labeled clearly to prevent confusion with prior versions.

Troubleshooting

• Can’t find the order: Include Final in the Status filter; broaden date range.
• Comment prompt didn’t appear: Ensure you selected the result row and opened Comments; use the Final Report Comments tab.
• Recipients didn’t get the corrected report: Verify you released the correction and check delivery logs; requeue if needed.