Building a Standardized Cancer Synoptic Report With Semantic and Syntactic Interoperability: Development Study Using SNOMED CT and Fast Healthcare Interoperability Resources (FHIR)
Bibliographic record
Abstract
Background: Pathology reports contain critical information necessary for the management of cancer patient care. Efforts to structure pathology cancer reports by the College of American Pathologists and the International Collaboration on Cancer Reporting (ICCR) have been successful in standardizing pathology reports. Likewise, standards development organizations have advanced methods to improve data computability and exchange, by enabling interoperability of pathology cancer reports. Objective: This study aimed to provide a tractable method to render pathology cancer reports computable and interoperable using published cancer reporting protocols, SNOMED Clinical Terms (SNOMED CT) and Health Level 7 (HL7) Fast Healthcare Interoperability Resources (FHIR). Methods: The ICCR colorectal cancer (CRC) reporting dataset (version 1.0) was evaluated by terminologists and pathologists. SNOMED CT concepts were bound to the data elements. The dataset was then converted into a FHIR structured data capture (SDC) questionnaire using the United States National Library of Medicine tooling and rendered into a FHIR-conformant message for data exchange. Results: The ICCR CRC dataset contained 216 data elements; 207 data elements were bound to SNOMED CT and incorporated into a FHIR SDC construct. The 9 uncoded data elements were ambiguous and could not be reliably encoded. The resultant FHIR SDC form fully represented the ICCR CRC dataset and rendered these data in an R4 JSON format for data exchange. Conclusions: This study demonstrates a tractable and extensible approach to making cancer pathology reports fully computable and interoperable that can be broadly adopted. ICCR datasets are supported internationally and supported by multiple national pathology societies. These datasets can be fully represented using SNOMED CT to render data elements computable and semantically faithful to their intended meaning. The use of the FHIR SDC construct enables widespread and standardized data exchange of clinical information. While challenges remain, including FHIR adoption and the need to maintain current clinical content and standard terminology, this approach provides a clear pathway toward implementation.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".