Review and release results - options, workflow, and distribution

After entering results (manually or via instrument/interface), use the Review/Release tools to finalize reporting. Distribution to clients and the web portal occurs only after results are released.

What each action means

• Mark as Reviewed (no release)
  • Records that a qualified user has reviewed the results.
  • Status remains Preliminary; no external distribution occurs.
• Review and Release
  • Marks results as reviewed and changes their status to Final.
  • Triggers report distribution per Client Report Rules (fax/portal/HL7/email).
• Scope: All vs. Selected
  • Release All: Finalizes every eligible result in the current order/worklist.
  • Release Selected: Finalizes only the orders/tests you’ve highlighted-useful for partial releases when some components are still pending.

Typical workflow (step-by-step)

1. Load the worklist (Results → Result Entry or Result Review) and apply filters (date, client, test, status).
2. Resolve validation items:
   • Missing units/reference ranges, flagged outliers, delta checks, critical value documentation.
   • For calculated results, use Refresh Ratio (or equivalent) after editing source values.
3. Optional: Click Mark as Reviewed if you’re completing verification but not ready to release.
4. Choose Release scope:
   • Select specific tests for partial release, or choose Release All for the order.
5. Confirm and release:
   • Add any final comments if needed.
   • The system updates status to Final and initiates distribution.
6. Verify delivery:
   • Check delivery logs/ACKs for fax, portal, and HL7 (requeue if failures are reported).

Distribution behavior

• Triggers on release:
  • Client Report Rules execute (fax/secure email/portal/HL7).
  • Web portal visibility switches on for released results only.
• Partial releases:
  • Sends an interim report with available finals; remaining tests can be released later.
• Holds:
  • If Hold Results is active on the order, release is blocked until the hold is cleared.

Corrections and addenda

• Corrected results:
  • Use the Correct/Amend function to update a previously released result.
  • System creates a Corrected report and redistributes to all configured destinations.
    

Quality and safety checks

• Reference range and delta check review
• Critical value workflow:
  • Document call-outs (who/when/outcome) before releasing critical results.
• Consistency:
  • Units, method, performing site, and dates (collected/performed/resulted) complete and accurate.

Permissions, audit, and compliance

• Role-based access controls:
  • Some labs require dual sign-off for specific departments/tests.
• Audit trail:
  • Every review/release records user, timestamp, before/after values, comments, and distribution events.
• PHI safeguards:
  • Distribution follows your privacy policies; avoid PHI in unsecured channels.

Best practices

• Use “Reviewed only” when awaiting additional components, provider clarification, or QC checks.
• Prefer partial release for time-sensitive results (e.g., critical values, STAT components).
• Include concise, standardized comments to guide interpretation.
• Verify delivery logs post-release and promptly requeue any failures.
• For send-outs, record the external performing lab and attach the source report when applicable.

With these controls, you can verify results safely, release them in the right order and scope, and ensure timely, compliant distribution to clients and the portal.