Patoloji ve Bilişim
The group’s pathology-informatics workstream: essays, notes, and the public content site
patoloji-hakkinda— pathology explainers.patoloji-ve-bilisim— pathology & informatics.rutinde-dijital-patoloji— digital pathology in routine practice.
Repository
What lives here
- Essays on digital pathology adoption, scanner operations, PACS integration.
- Practical notes on interfacing QuPath, Sectra, and LIS in routine work.
- Reference material on DICOM, HL7, SNOMED, and reporting standards.
- Workflow case studies drawn from Memorial operations.
Contribution flow
- Pick a topic that either:
- resolves a real operational question someone asked, or
- documents an architecture decision that will otherwise be lost.
- Draft in Turkish (primary). English abstract optional.
- Cross-link to the primary-source repo (scanner project, consultation project, LIS notes) rather than duplicating content.
Conventions
- No PHI, ever. Operational case studies describe processes, not patients.
- One decision, one page. If an essay is describing more than one design decision, split it.
- Link to code, don’t paste code. Code lives in the project repo; this site summarizes and contextualizes it.
In the research wiki
- Patoloji Bilgi Yönetim Sistemi (LIS) — the LIS notes repository, and the structural half of this workstream.
- Memorial LIS Extracts — the research-facing output of that system, with its documented reliability caveats.
- Synoptic Reporting — the informatics payoff of structured reporting: completeness first, machine-readability as a side effect.
- Server-Side Slide Platforms — what it takes to move image work off single workstations, which is the same conversation one layer up.
- De-identification — the constraint every informatics design here runs into.
- Report Text Extraction — the practical bridge between narrative reports and anything analysable.