Reviewing and accepting interfaced results

Use the Result Interface screen to review and accept results received from instruments or middleware. It closely mirrors the Manual Result Entry form, with one key difference: manual typing of results is disabled. Instead, you select the appropriate instrument run and accept it into the order.

Key differences vs. Manual Result Entry

• No manual entry: Values come from the interface only; you cannot type over them.
• Run selection: A dedicated Run column shows available repeats/replicates from the instrument. You select the satisfactory run for each test.
• Accept/commit workflow: Click Update to stage your selections, then Save to commit them to the order.

Screen layout

• Orders grid (top): The orders you’re working on.
  

• Run column (e.g., 1, 2, 3) for multiple runs

• Tests/Results grid (bottom): Interfaced results with:
  • Value, Units, Reference Range, Flags (H/L/Critical)
  • Instrument/Device, Performed/Resulted times
  • Status (Pending Review, Final)

Typical workflow

1. Open and load worklist

   • Go to Results → Result Interface.
   • Click Search, set filters (date range, instrument, client/site, test, status), then Find.
   • Select orders and click Done.

2. Review incoming results

   • For each test, evaluate value, units, reference range, instrument flags, and deltas from prior results.
   • If multiple instrument runs exist, review their values and flags.

3. Select the satisfactory run

   • Choose the desired run in the Run column (e.g., Run 2 if Run 1 flagged alerts in the instrument).
   • Optional: Add a result comment when applicable.

4. Update (accept) and commit

   • Click Update to accept the selected run(s) for the highlighted rows. Note that you can apply this actions to all orders, selected orders or specific tests.
   • When finished, click Save to commit selections to the order.
   • Depending on your policy:
     • Leave as Preliminary and route to Review/Release, or
     • If autoverification is configured and criteria are met, results may finalize automatically.

5. Release (if applicable)

   • Use Review and Release to finalize and distribute results (fax/portal/HL7) once verification is complete.

Batch actions

• Multi-select rows of the same test/analyte and pick a run once; use Update to apply in bulk.
• Filter by instrument/test/status to build focused worklists for high-throughput acceptance.
• Use saved views for recurring work (e.g., “Chemistry—Analyzer A—Today”).

Validation, QC, and safety checks

• Auto-flags: High/low/critical markers and instrument flags are displayed.
• Delta checks: Visual cues for significant change from prior results.
• Critical values: If a selection yields a critical result, follow the critical value workflow before release.

Comments and documentation

• Result comments: Add brief report-visible comments when context is needed (e.g., “Hemolysis index elevated; interpret K+ with caution”).
• Internal notes: Use internal-only comments for verification rationale.
• All actions are audit-logged (who, when, selected run, before/after).

Exceptions and unmatched results

• Unmatched results queue: If a result can’t be mapped to an order/test (code mismatch). Resolve mapping, then accept.
• Mapping issues: Ensure instrument/middleware test codes are correctly mapped to LIS tests.

Best practices

• Always review instrument flags and QC context before accepting a run.
• Prefer the most recent valid run that meets QC—document your rationale when not selecting the latest run.
• Use Hold Results on the order if additional review or recollection is required.
• Do not attempt to “correct” interfaced values by notes—reject or request re-run instead, per policy.
• For send-outs or manual backups, switch to Manual Result Entry.