HL7 vs Non-HL7 in Outpatient Imaging QC

Same Pending queue, different evidence lanes

Sites in the same imaging network may send very different records with a study. One facility may supply a structured order feed. Another may rely on tech sheets, scanned forms, or notes stored with the exam. In either case, the PACS admin has to determine whether the record is complete enough to leave Pending.

Study readiness covers operational checks such as order agreement, laterality, reason for exam, required documents, and open holds. It does not include diagnostic interpretation. The checklist is outlined in What makes a study read-ready. A site's integration mode determines which approved sources can satisfy each check.

What "HL7 site" means for Pending QC

At an HL7 site, controlled policy expects structured order-feed evidence for specific readiness checks. If that evidence is absent, the case should be flagged. A free-text note can serve as a substitute only when site policy approves it for that check.

In the Pending queue, that can mean:

• A blank or stale order-feed field can keep a study in Pending even when the images appear complete.
• Reason-for-exam and case-type checks may require the structured intake path. A tech comment that mentions the indication may not be sufficient.
• Fixing the problem may require help from registration, order entry, or interface monitoring rather than a change in PACS.

PACS admins own the last mile because they can see when the feed failed, which tag or status is holding the study, and who owns the correction.

What changes at a non-HL7 site

At a non-HL7 site, policy names the tech sheets, current documents, forms, or notes that may supply required context. Staff review those approved sources instead of relying on a structured feed for every lane-dependent check. The QC standard still applies.

The operating rules should cover three points:

1. Name the approved sources. Record which tech sheets, forms, documents, and note fields are in scope. A populated field is not automatically sufficient evidence.
2. Send uncertain cases to review. An unreadable scan, an outdated form, or conflicting notes cannot support a pass.
3. Assign remediation clearly. Chasing a document and fixing an order feed require different owners. Tracking them separately shows where the process is failing.

The failure mode: treating missing HL7 as non-HL7

A missing feed should not send a case into the non-HL7 path by default. If policy expects HL7 evidence and the feed is authoritatively absent, the case is blocked or needs review. An unresolved site mapping also needs review. Staff may use a note as fallback evidence only when policy approves that source for the check.

Sending a case down the wrong lane can contribute to the cost of incomplete studies reaching the reader, including callbacks, rework, and delayed turnaround. Track how often interface failures are mislabeled as document problems; the result can point to the team and system that need attention.

How Corena keeps the lanes separate

Corena runs operational Pending QC before reading. Site policy records the lane as HL7, non-HL7, or unresolved. A lane-dependent check goes to review when policy or source evidence is missing, conflicting, or stale. Corena does not infer facility mappings or interpret images, and a missing HL7 message never serves as proof of a non-HL7 lane.

To compare how your sites establish readiness across HL7 and non-HL7 workflows, request a demo. Start with real Pending cases and keep writes disabled, following the approach in read-only before writeback.