Posts

Showing posts with the label LOINC

Building Evidence-Based Clinical Pathways with SNOMED CT, LOINC, CQL, and HL7 FHIR R5

 Abstract The computerization of evidence-based clinical pathways requires more than translating narrative recommendations into simple “if–then” statements. A reliable implementation must preserve the meaning of clinical observations, diagnoses, interventions, timing constraints, exceptions, and evidence provenance while integrating with Electronic Health Record (EHR) and Laboratory Information System (LIS) workflows. SNOMED CT and LOINC aprovide complementary semantic foundations for this work. LOINC is commonly used to identify laboratory tests, clinical measurements, and other observations, whereas SNOMED CT represents clinical findings, disorders, organisms, procedures, and many qualitative result values. HL7 FHIR R5 provides the structural resources for representing knowledge artifacts, while Clinical Quality Language (CQL) supplies executable patient-level logic. This essay proposes a reference architecture consisting of a terminology server, a clinical pathway or knowledge-a...

Semantics, Ontology, and Syntax in Health Informatics: Conceptual Distinctions and Practical Implications for Hospital EHR Implementation

Abstract Implementing a modern Electronic Health Record (EHR) in a hospital is fundamentally an exercise in representing, exchanging, and reusing clinical information safely across time, teams, and systems. This requires clarity about three related but distinct notions: syntax (how information is structured and encoded), semantics (what that structured information means), and ontology (a formal, explicit specification of the domain concepts and relations that underpin shared meaning and enable computational reasoning). In this essay I want to distinguish these concepts and demonstrates how their differences translate into concrete design, integration, governance, and patient-safety considerations in real-world hospital EHR implementations. 1. Introduction Hospitals depend on EHRs not only to store a longitudinal patient record, but to coordinate care across departments (e.g., laboratory, pharmacy, radiology, admissions), across professions, and often across organizational boundaries...

Vereisten van een modern EPD: administratieve lastreductie én datagedreven klinische meerwaarde

Inleiding Elektronische patiëntendossiers (EPD’s) zijn tegelijk een cruciale infrastructuur voor veilige zorg en een bekende bron van administratieve belasting. In de literatuur wordt documentatiebelasting expliciet in verband gebracht met burnout, lagere tevredenheid en “work outside of work” (o.a. avond- en weekendregistratie). Daarnaast wordt slechte EPD-bruikbaarheid geassocieerd met hogere belasting en ongunstige werkervaringen. Tegen deze achtergrond ontstaat een dubbele ontwerp- en governance-opgave: (i) minimaliseer registratielast voor artsen en verpleegkundigen, en (ii) maximaliseer de klinische herbruikbaarheid van data zodat zorgprocessen daadwerkelijk datagedreven kunnen worden ondersteund (kwaliteit, veiligheid, continuïteit, populatiemanagement). Hier doe ik een bescheiden persoonlijke poging om m.i. enige relevante elementen te formuleren waaraan een modern EPD idealiter zou kunnen voldoen om beide doelen simultaan te realiseren. De eisen worden benaderd als een socio-t...