HL7 for cancer registry and pathology reporting

Cancer reporting is not generic pathology HL7; it is profile-driven, coded, and audit-heavy.

Cancer registry and pathology reporting is the highest-risk topic in this article set because the details are jurisdictional and profile-driven. It is safe to say that many workflows use constrained pathology reporting based on ORU_R01-style structures, OBR/OBX observations, specimen context, coded values, and narrative text. It is not safe to invent the receiving registry's profile.

NAACCR publishes pathology laboratory electronic reporting guidance, including current Volume V material and historical HL7 v2.5.1 implementation guidance for synoptic reports. Use that or the receiving registry's exact guide. Treat this article as orientation, not as a substitute for a registry implementation guide.

MSH|^~\&|PATH|CITYLAB|REGISTRY|STATE|20260715180000||ORU^R01^ORU_R01|CA000501|P|2.5.1 PID|1||123456^^^CITYHOSP^MR||Smith^Jane^Anne^^Ms^^L||19800314|F ORC|RE|PATH4488^EHR|PATH7788^LIS OBR|1|PATH4488^EHR|PATH7788^LIS|60568-3^Pathology Synoptic report^LN|||20260714100000|||||||||67890^Pathologist^Pat^^^^^^NPI||||||20260715174500|||F SPM|1|SPEC7788^LIS||TISS^Tissue^HL70487|||||||P||||||20260714100500 OBX|1|TX|33732-9^Histology report final diagnosis^LN||Invasive ductal carcinoma.||||||F|||20260715170000 OBX|2|CE|21908-9^Primary tumor site^LN||C50.9^Breast, unspecified^ICD-O-3||||||F|||20260715170000 OBX|3|NM|44667-5^Tumor size greatest dimension^LN||18|mm|||||F|||20260715170000

This is synthetic sample data for learning and testing. Open it in HL7 Soup Web before mapping it so the segment groups, repeated fields, and coded values are visible.

This Is Profile-Driven Work

Generic ORU_R01 knowledge is necessary but not sufficient. The registry profile determines required segments, observation identifiers, code systems, cardinality, conformance rules, and the mapping from pathology content into registry data items. A message that looks reasonable to an EHR may still be useless to a registry if the synoptic elements are missing or uncoded.

For cancer pathology, preserve both the narrative diagnostic text and the discrete coded values. Registrars and automated registry workflows may need different parts of the same report.

  • Keep specimen context in SPM or profile-specific fields.
  • Preserve OBR service/report identity and status.
  • Do not strip OBX identifiers, value type, code system, units, or status.

Synoptic And Narrative Need To Coexist

A pathology report may carry a final diagnosis paragraph, tumor site, histology, grade, margins, lymph nodes, biomarkers, and staging-related data. Some are text; some are coded observations. The interface should not choose one representation and discard the other unless the receiving guide explicitly says so.

A Practical Integration Soup Workflow

In Integration Soup, build a validation-first workflow: receive pathology ORU messages, preserve raw input, map required discrete elements, log missing required observations, and quarantine messages that fail registry conformance instead of sending bad data silently.

Use HL7 Soup Web to inspect OBR/OBX/SPM structure and the repeating OBX tutorial pattern when exporting one row per observation for review.

The Test Pack I Would Ask For

Ask for a minimal report, complete synoptic report, amended report, report with multiple specimens, report with missing required synoptic item, coded and narrative values, and registry ACK/rejection examples.