Cancer Electronic Pathology Reporting & IHE SDC/eCC on FHIR
This project will use FHIR to support structured electronic exchange of cancer pathology information between a hospital or facility-based laboratory information system (LIS) and hospital or facility-based electronic health record (EHR) system to a Central Cancer Registry (CCR). The goal of this project is to create one FHIR implementation guide (US Realm) that will complement the currently accepted and widely implemented V2 and NAACCR Standards for Cancer Registries Volume V, Laboratory Electronic Reporting Pathology Version 5, May 2020 (Revised 2020). We will be aligning with the IHE SDC/eCC on FHIR IG and their testing efforts.
Continued testing of alignment between IHE SDC/eCCs on FHIR and Cancer E-Pathology Reporting IGs, as well as use of a backend services app to facilitate reporting to a registry.
Call for participants
Understanding of Message Bundles, Observations, & DiagnosticReports required:
Sandy Jones, Alex Goel, Dave deRoode, Caitlin Kennedy
Track Lead Email(s)
Track Kick off Call
December 14, 10:00am EST
Microsoft Teams meeting
Join on your computer, mobile app or room device
Meeting ID: 293 201 171 968
Or call in (audio only)
+1 404-498-3000,,263989990# United States, Atlanta
(888) 994-4478,,263989990# United States (Toll-free)
Phone Conference ID: 263 989 990#
If you missed the Kick-Off Call, then please see the recording and slides below: HL7 FHIR Cancer Pathology Data Sharing WG-20221214_100540-Meeting Recording.mp4
Previously, we simulated a path lab generating a completed synoptic report (through the SDC form filler) and tested turning that into FHIR observations and then wrapping it in a FHIR Bundle. The bundle included Observations, Patient, DiagnosticReport, and MessageHeader. We tested submitting this bundle to an EHR and/or CCR. We also tested the Order of the collection of the Specimen, the collection of the Specimen itself (process and procedure), and the ordering of the path lab analysis, as well as a lab system producing the results of these analysis and send it outbound either to an EHR or to a central registry via collection Bundle.
2. (Re-testing) the use of a HDEA to receive a trigger code (PlanDefinition), query an LIS, compile a pathology report via our bundling, and pushing it to a cancer registry/CCR.
3. EHR to EHR: Test the compiling and sending (POST) to a 3rd party EHR FHIR server.
Security and Privacy Considerations: