<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>semantic interoperability &#8211; Science</title>
	<atom:link href="https://scienmag.com/tag/semantic-interoperability/feed/" rel="self" type="application/rss+xml" />
	<link>https://scienmag.com</link>
	<description></description>
	<lastBuildDate>Thu, 15 Oct 2026 12:49:25 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>

<image>
	<url>https://scienmag.com/wp-content/uploads/2024/07/cropped-scienmag_ico-32x32.jpg</url>
	<title>semantic interoperability &#8211; Science</title>
	<link>https://scienmag.com</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">73899611</site>	<item>
		<title>AI Checklists Stop at the Model: Why Semantic Governance in Clinical Labs Ends Before Deployment</title>
		<link>https://scienmag.com/ai-checklists-stop-at-the-model-why-semantic-governance-in-clinical-labs-ends-before-deployment/</link>
		
		<dc:creator><![CDATA[Courtney Benton]]></dc:creator>
		<pubDate>Thu, 15 Oct 2026 12:49:25 +0000</pubDate>
				<category><![CDATA[Medicine]]></category>
		<category><![CDATA[AI interpretability in healthcare]]></category>
		<category><![CDATA[AI model deployment in clinical laboratories]]></category>
		<category><![CDATA[AI model drift and monitoring]]></category>
		<category><![CDATA[AI model validation challenges]]></category>
		<category><![CDATA[Artificial Intelligence]]></category>
		<category><![CDATA[clinical decision support]]></category>
		<category><![CDATA[clinical lab AI safety]]></category>
		<category><![CDATA[FHIR]]></category>
		<category><![CDATA[governance]]></category>
		<category><![CDATA[health informatics]]></category>
		<category><![CDATA[healthcare AI governance]]></category>
		<category><![CDATA[Japan's JLAC11 code list]]></category>
		<category><![CDATA[JLAC11]]></category>
		<category><![CDATA[laboratory code standards]]></category>
		<category><![CDATA[laboratory data standardization]]></category>
		<category><![CDATA[laboratory measurement methods]]></category>
		<category><![CDATA[laboratory medicine]]></category>
		<category><![CDATA[model]]></category>
		<category><![CDATA[post-deployment AI oversight]]></category>
		<category><![CDATA[post-deployment surveillance]]></category>
		<category><![CDATA[Semantic]]></category>
		<category><![CDATA[semantic governance in AI]]></category>
		<category><![CDATA[semantic interoperability]]></category>
		<category><![CDATA[Stops]]></category>
		<guid isPermaLink="false">https://scienmag.com/?p=273899</guid>

					<description><![CDATA[A new Journal of Medical Systems commentary argues that laboratory-aware AI checklists stop at the model, leaving semantic stability after deployment to oversight frameworks never designed for it.]]></description>
										<content:encoded><![CDATA[<p>A new commentary in the Journal of Medical Systems argues that the checklists designed to make artificial intelligence laboratory-aware stop working the moment a model leaves the bench, leaving a critical gap in post-deployment oversight. Koichiro Yuji and Wakako Yuji, writing in a Comment published on 15 October 2026, contend that semantic governance—the careful alignment of what laboratory codes, units, and methods actually mean—stops at the model itself, and that everything downstream of validation is left to post-deployment surveillance frameworks that were never designed to carry that burden.</p>
<p>The authors ground their argument in the JLAC11 code list, Japan&#8217;s 17-digit laboratory code standard maintained by the Japan Society of Laboratory Medicine. Drawing on version 1.2 of the publicly available list, they counted rows, distinct codes, and method codes per combination of analyte and specimen, and compared the method name with the product name in each row. The point of this exercise is not bookkeeping for its own sake: it is to show that the same analyte measured on the same specimen can be reported under codes that embed different measurement methods, and that an AI model trained on one method&#8217;s distribution may silently misinterpret another&#8217;s.</p>
<p>This is where the commentary&#8217;s central claim bites. Laboratory-aware AI checklists, such as the EFLM checklist for the assessment of AI and machine learning studies in laboratory medicine published in Clinical Chemistry and Laboratory Medicine, have made real progress in forcing researchers to specify data provenance, preanalytical conditions, and analytical platforms before a study is accepted. But Yuji and Yuji argue that these checklists are, by design, pre-deployment instruments. They ask whether the right things were documented before the model was built. They do not ask whether the meaning of the data flowing into the model will remain stable after the model is running in a live hospital information system.</p>
<p>The authors connect this gap to Japan&#8217;s ongoing push for electronic health records and electronic prescriptions. The Ministry of Health, Labour and Welfare set targets in August 2025 for electronic prescriptions and electronic health records, and the Japan Association for Medical Informatics has published the JP-CLINS FHIR implementation guide for the Electronic Health Record Information Sharing Service. An Act amendment consolidated in force from 1 October 2026 added provisions to the Act on Promotion of Comprehensive Securing of Medical and Long-Term Care in the Community. Together, these regulatory and technical moves are pushing laboratory data into shared FHIR-based infrastructure at unprecedented scale, which means the semantic quality of laboratory codes is no longer a local concern but a national one.</p>
<p>Yuji and Yuji&#8217;s argument draws on a body of recent work in the same journal and adjacent outlets. Perdomo Lampignano and colleagues wrote in 2026 about operationalising post-deployment surveillance of AI medical devices in clinical practice, arguing that validation alone is insufficient. Ver Berne and Jacobs asked when useful clinical AI exceeds meaningful oversight. Dong and colleagues examined how clinical readiness claims derived from medical AI benchmark results should be governed. Sorin and Klang insisted that clinical AI generators and reviewers must be tested together. Shujaat argued for lifecycle assurance for clinical artificial intelligence beyond regulatory approval. Each of these pieces, the commentary suggests, points toward the same conclusion: the hard part of AI governance in medicine is not what happens before deployment but what happens after.</p>
<p>But the commentary adds a twist that these frameworks do not fully address. Post-deployment surveillance typically monitors model performance—accuracy, drift, calibration—against a fixed reference. Yuji and Yuji argue that in laboratory medicine, the reference itself is unstable. Hemolyzed specimens, a well-documented challenge for emergency departments and clinical laboratories since Lippi and colleagues&#8217; 2011 review, can shift analytical results in ways that depend on the measurement method. Plebani, Laposata, and Lundberg&#8217;s brain-to-brain loop concept for laboratory testing, introduced forty years before their 2011 reflection, already recognised that laboratory results are not static objects but part of a communicative process between clinician and laboratory. An AI model embedded in that loop inherits all of its instabilities.</p>
<p>The commentary also engages with the question of metrological and algorithmic traceability. Li and Plebani, writing in the Journal of Clinical Laboratory Analysis in 2026, examined how machine learning in laboratory medicine can be made traceable both metrologically and algorithmically. Padoan and colleagues asked whether metadata and peridata in clinical laboratory data flows could bridge the gap to new AI-based applications. Park, Kim, and Badrick and colleagues addressed property and unit discordance in laboratory interoperability, proposing NPU as a governance layer. Naliyatthaliyazchayil and Stenerson harmonized LOINC codes and units in real-world oncology data. Okada and Yamamoto mapped LOINC and Japan&#8217;s JLAC standard using generative AI for international collaborative research. Each of these efforts, the commentary implies, is trying to stabilise meaning—but stabilising meaning is a continuous process, not a checklist item.</p>
<p>Yuji and Yuji&#8217;s own prior work frames the stakes. In a 2026 piece in Clinical Chemistry and Laboratory Medicine, they argued that artificial general intelligence and the clinical laboratory represent a paradigm shift toward Lab 2.0, echoing Crawford and colleagues&#8217; 2017 Project Santa Fe report on clinical lab 2.0. If laboratories are moving toward a model where AI is not just a tool but a participant in the diagnostic process, then the semantic quality of the codes that AI reads becomes a first-order clinical safety issue, not a technical detail. The commentary&#8217;s title—Semantic Governance Stops at the Model—is a deliberate provocation: the checklists that govern what AI should know about the laboratory stop working once AI is deployed, and the frameworks that govern deployed AI do not know enough about the laboratory.</p>
<p>The authors are explicit that they are not calling for the abolition of checklists. The EFLM checklist and the comprehensive checklist for the self-assessment of medical AI studies introduced by Cabitza and Campagner in 2021 have improved the quality of medical informatics research. Rather, the commentary argues that checklists are necessary but insufficient, and that the remaining work—ensuring that the meaning of laboratory data remains stable and interpretable after deployment—must be carried by post-deployment oversight frameworks that are currently not equipped for it. The authors received no external funding for the submitted work, and the Comment did not involve human participants, human data, or animals.</p>
<p>The commentary&#8217;s practical implication is stark. As Japan and other health systems push laboratory data into shared FHIR infrastructure, and as AI models are deployed against that data at scale, the gap between pre-deployment checklists and post-deployment surveillance becomes a live clinical safety issue. Yuji and Yuji&#8217;s contribution is to name that gap precisely: semantic governance stops at the model, and everything after the model is left to oversight frameworks that were never designed to carry the weight of laboratory meaning. Whether post-deployment surveillance can be redesigned to carry that weight is the question the commentary leaves open.</p>
<p><strong>Subject of Research:</strong> Semantic interoperability and post-deployment oversight of AI in laboratory medicine</p>
<p><strong>Article Title:</strong> Semantic Governance Stops at the Model: What Laboratory-Aware AI Checklists Leave to Post-Deployment Oversight</p>
<p><strong>Article References:</strong> Semantic Governance Stops at the Model: What Laboratory-Aware AI Checklists Leave to Post-Deployment Oversight. (n.d.). <a href="https://doi.org/10.1007/s10916-026-02478-y" rel="noopener noreferrer">https://doi.org/10.1007/s10916-026-02478-y</a></p>
<p><strong>Image Credits:</strong> AI Generated</p>
<p><strong>DOI:</strong> <a href="https://doi.org/10.1007/s10916-026-02478-y" rel="noopener noreferrer">10.1007/s10916-026-02478-y</a></p>
<p><strong>Keywords:</strong> artificial intelligence, laboratory medicine, semantic interoperability, post-deployment surveillance, clinical decision support, health informatics, JLAC11, FHIR, Semantic, Governance, Stops, Model</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">273899</post-id>	</item>
		<item>
		<title>AI Assistant Helps Human Coders Map Clinical Text to SNOMED CT Twice as Fast</title>
		<link>https://scienmag.com/ai-assistant-helps-human-coders-map-clinical-text-to-snomed-ct-twice-as-fast/</link>
		
		<dc:creator><![CDATA[Ophelia Keating]]></dc:creator>
		<pubDate>Fri, 02 Oct 2026 10:10:00 +0000</pubDate>
				<category><![CDATA[Medicine]]></category>
		<category><![CDATA[AI and human collaboration in medical data coding]]></category>
		<category><![CDATA[AI-assisted clinical coding]]></category>
		<category><![CDATA[automated medical concept recognition]]></category>
		<category><![CDATA[bilingual clinical text]]></category>
		<category><![CDATA[clinical terminology mapping]]></category>
		<category><![CDATA[computational methods for medical coding]]></category>
		<category><![CDATA[electronic health records]]></category>
		<category><![CDATA[enhancing electronic health records interoperability]]></category>
		<category><![CDATA[GPT-4]]></category>
		<category><![CDATA[health information management]]></category>
		<category><![CDATA[healthcare data integration and AI]]></category>
		<category><![CDATA[Human-AI Collaboration.]]></category>
		<category><![CDATA[improving accuracy of clinical terminology mapping]]></category>
		<category><![CDATA[large language models]]></category>
		<category><![CDATA[machine learning for clinical text annotation]]></category>
		<category><![CDATA[mapping medical texts to SNOMED CT]]></category>
		<category><![CDATA[medical coding]]></category>
		<category><![CDATA[natural language processing in healthcare]]></category>
		<category><![CDATA[reducing clinical documentation errors]]></category>
		<category><![CDATA[retrieval-augmented generation]]></category>
		<category><![CDATA[semantic interoperability]]></category>
		<category><![CDATA[SNOMED CT]]></category>
		<category><![CDATA[SNOMED CT standardization in healthcare]]></category>
		<category><![CDATA[vector database]]></category>
		<guid isPermaLink="false">https://scienmag.com/?p=227063</guid>

					<description><![CDATA[A human-AI collaborative workflow developed at Seoul National University Hospital improved SNOMED CT mapping accuracy for bilingual clinical text while cutting coding time by more than half.]]></description>
										<content:encoded><![CDATA[<p>Every time a hospital record says &#8220;ESKD on NIPD,&#8221; somewhere a trained specialist has to decide exactly which standardized medical concepts those cryptic letters represent. It is tedious, error-prone work, and it sits at the heart of one of modern medicine&#8217;s quietest bottlenecks: turning messy, free-text clinical notes into the standardized vocabulary that lets computers, hospitals, and researchers speak the same language. A new study from Seoul National University Hospital, published in the Journal of Medical Systems, suggests that a carefully engineered collaboration between human experts and a large language model can crack that bottleneck, boosting accuracy while cutting the work in half.</p>
<p>The standardized vocabulary in question is SNOMED CT, the Systematized Nomenclature of Medicine–Clinical Terminology, an international reference containing 368,285 active concepts spanning diagnoses, procedures, findings, and the hierarchical relationships among them. When clinical narratives are mapped to SNOMED CT concepts, electronic health records become computable, multi-center data integration becomes feasible, and the growing appetite of clinical artificial intelligence for machine-interpretable data can be satisfied. The trouble is that mapping has traditionally been done by hand, one phrase at a time, and studies have shown that even professional coding services disagree with one another to a striking degree when assigning concepts to the same text.</p>
<p>Researchers led by Hyeonhoon Lee and Hyung-Chul Lee built an agent system on the LangChain framework using GPT-4 Turbo as its underlying model, and designed it not to replace human coders but to widen their field of view. The system processes each piece of clinical text through three sequential modules. A Translation Module detects the language and converts Korean or mixed Korean–English passages into English while preserving medical terms already written in English, consulting external web search tools when phrases are ambiguous. An Abbreviation Expansion Module then resolves domain-specific acronyms using the clinical category and department as context, so that &#8220;PCI&#8221; becomes &#8220;Percutaneous Coronary Intervention&#8221; in a cardiology setting but can be expanded differently elsewhere. Finally, a Retriever Module encodes the normalized text with MedCPT, a biomedical transformer model, and searches a pre-embedded vector database of SNOMED CT concepts using cosine similarity, returning the twenty best-matching candidate concepts.</p>
<p>The test bed was real and demanding. From 85,031 discharge cases at the tertiary academic hospital between March 2022 and June 2024, the team assembled 2,261 de-identified free-text segments drawn from complex disease assessment forms, spread evenly across nine clinical categories ranging from symptoms and medications to advanced procedures and underlying diseases. The segments were brutally short, with a median of just twelve characters and two words, packed with abbreviations. A reference panel of three professional health information managers, later joined by a physician professor of medical informatics, independently assigned consensus SNOMED CT concepts to every segment in two blind adjudication rounds, and about half the segments turned out to require more than one concept.</p>
<p>Three health information managers then mapped the same segments under three conditions: entirely by hand using the SNOMED CT Browser, entirely by the agent alone, and with the agent&#8217;s top-twenty candidate list presented through a custom web interface that let them select, modify, or reject any suggestion. The results were unambiguous. The agent-assisted approach achieved a pooled hit rate at rank one of 0.868, beating both unassisted human mapping at 0.837 and the agent alone at 0.701, with all differences statistically significant. On R-precision, a metric that adapts to the number of correct concepts each segment carries, the collaborative workflow scored 0.674 against 0.632 for humans working alone. The agent by itself was reliably worse than the experts, confirming that fully automated coding is not yet ready to fly solo.</p>
<p>The efficiency gains were even more dramatic. Total mapping time fell 53.9 percent, from 59.2 hours to 27.3 hours for the full dataset, or from 1.57 minutes to 0.72 minutes per segment once the agent&#8217;s own processing time of about eleven seconds per segment was included. The reduction held across every clinical category, ranging from 35.8 percent for advanced treatment text to 64.6 percent for symptom descriptions, and every individual mapper saved between roughly 52 and 57 percent of their previous working time. For terminology standardization programs, where manual coding is a chronic resource drain, those numbers translate directly into capacity.</p>
<p>Perhaps the most intriguing finding lies in how the collaboration changed human behavior. Mappers selected about 79 percent of their final concepts directly from the agent&#8217;s candidate list, typically from the top few ranks, but a full 21 percent they still hunted down independently through the SNOMED CT Browser, showing that the experts were thinking beyond the machine&#8217;s suggestions. The authors argue that the key mechanism is an expansion of the space of valid candidates: the agent surfaced correct concepts that mappers would never have found through conventional keyword search, letting them pick different but individually valid answers when multiple correct options existed. Consistent with that interpretation, agreement between mappers, measured by the Jaccard index, dropped from 0.915 to 0.639 under assistance, and plunged to 0.450 for segments requiring multiple concepts, precisely where the space of legitimate answers is widest.</p>
<p>The architecture also carries practical advantages for real hospitals. The vector database of SNOMED CT concepts runs entirely on local infrastructure with no external calls during retrieval, and because SNOMED CT is updated monthly, the system stays current simply by refreshing the database rather than retraining any model, a sharp contrast with supervised entity-linking approaches that require labeled clinical notes. The translation and abbreviation modules do currently rely on proprietary external APIs, which the authors acknowledge would need locally hosted open-source replacements for deployments under strict data governance rules. The bilingual capability also addresses a recognized gap, since most terminology-mapping tools were built for English text alone.</p>
<p>The study is honest about its limits. It unfolded at a single institution with three mappers, segments were mapped in isolation without the surrounding clinical record, the two conditions ran in fixed order separated by a four-month wash-out rather than counterbalanced, and the reference panel shared an institution with the mappers, so measured accuracy should be read as a plausible upper estimate. Mapping time was logged automatically in the assisted condition but self-reported in the manual one, introducing measurement asymmetry. Still, the subgroup analysis showed the collaborative approach winning on F1 in eight of nine clinical categories and in both single- and multi-concept strata, and the authors call for multi-center, prospective validation, additional language pairs, and open-source model substitution as next steps.</p>
<p>The broader lesson may outlast the specific technology. As large language models flood into medicine, the seductive promise is full automation, yet this study adds to mounting evidence that the highest-value configuration is neither machine nor human alone but a division of labor in which the machine generates and ranks possibilities while the expert retains judgment, context, and accountability. Here, that division produced something neither party achieved separately: more accurate standardized coding than experts working unaided, faster than anyone thought possible, and a template for how hospitals everywhere might finally tame their mountains of unstructured clinical text.</p>
<p><strong>Subject of Research:</strong> Human-AI collaborative large language model workflow for mapping bilingual clinical text to SNOMED CT concepts</p>
<p><strong>Article Title:</strong> Development and Validation of Human-AI Collaborative Workflow in SNOMED CT Mapping of Bilingual Clinical Text</p>
<p><strong>Article References:</strong> Lee, H., Choi, S., Kim, D., Hong, K., Kim, H., Jeong, C. W., &amp; Lee, H.-C. (2026). Development and Validation of Human-AI Collaborative Workflow in SNOMED CT Mapping of Bilingual Clinical Text. <em>Journal of Medical Systems, 50</em>(1), Article 141. <a href="https://doi.org/10.1007/s10916-026-02465-3" rel="noopener noreferrer">https://doi.org/10.1007/s10916-026-02465-3</a></p>
<p><strong>Image Credits:</strong> AI Generated</p>
<p><strong>DOI:</strong> <a href="https://doi.org/10.1007/s10916-026-02465-3" rel="noopener noreferrer">10.1007/s10916-026-02465-3</a></p>
<p><strong>Keywords:</strong> SNOMED CT, large language models, clinical terminology mapping, human-AI collaboration, retrieval-augmented generation, electronic health records, semantic interoperability, bilingual clinical text, health information management, vector database, GPT-4, medical coding</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">227063</post-id>	</item>
		<item>
		<title>Ocean Data Gets a FAIR Upgrade to Power Sustainable Seas</title>
		<link>https://scienmag.com/ocean-data-gets-a-fair-upgrade-to-power-sustainable-seas/</link>
		
		<dc:creator><![CDATA[Violet Maxwell]]></dc:creator>
		<pubDate>Sat, 12 Sep 2026 19:20:51 +0000</pubDate>
				<category><![CDATA[Marine]]></category>
		<category><![CDATA[autonomous ocean sensors]]></category>
		<category><![CDATA[biodiversity data]]></category>
		<category><![CDATA[data infrastructure]]></category>
		<category><![CDATA[data standardization in marine science]]></category>
		<category><![CDATA[digital ocean]]></category>
		<category><![CDATA[FAIR data principles]]></category>
		<category><![CDATA[FAIR principles]]></category>
		<category><![CDATA[governance frameworks for ocean data]]></category>
		<category><![CDATA[marine data repositories]]></category>
		<category><![CDATA[marine spatial data infrastructure]]></category>
		<category><![CDATA[Marine Spatial Planning]]></category>
		<category><![CDATA[microbial ocean ecosystems]]></category>
		<category><![CDATA[ocean data fragmentation]]></category>
		<category><![CDATA[ocean data governance]]></category>
		<category><![CDATA[Ocean data sharing]]></category>
		<category><![CDATA[Ocean Decade]]></category>
		<category><![CDATA[ocean observations]]></category>
		<category><![CDATA[Ocean sustainability]]></category>
		<category><![CDATA[open science]]></category>
		<category><![CDATA[open science in ocean research]]></category>
		<category><![CDATA[satellite ocean monitoring]]></category>
		<category><![CDATA[semantic interoperability]]></category>
		<category><![CDATA[Sustainable Ocean Management]]></category>
		<guid isPermaLink="false">https://scienmag.com/?p=197816</guid>

					<description><![CDATA[New research in npj Ocean Sustainability argues that aligning marine spatial data infrastructures with FAIR principles and open science is essential for building the equitable, machine-readable knowledge systems that sustainable ocean management demands.]]></description>
										<content:encoded><![CDATA[<p>The ocean has always been difficult to see. It hides its chemistry, its currents, and its creatures behind kilometers of water, and for centuries scientists have pieced together its behavior from scattered ship logs, tide gauges, and expeditions that might take years to complete. Today the picture is changing at extraordinary speed. Satellites map sea surface temperature in near real time, autonomous gliders drift through deep basins relaying profiles of salinity and oxygen, and genomic sequencers reveal entire microbial ecosystems from a single liter of seawater. Yet for all this technological abundance, a quieter crisis persists beneath the waves of information: the data itself remains fragmented, locked in incompatible formats, and scattered across national repositories, research cruises, and institutional hard drives that may outlive the projects that created them.</p>
<p>A new perspective article published in npj Ocean Sustainability argues that the next leap in ocean science will not come from another sensor or satellite, but from the infrastructure that connects the data we already have. The authors examine how marine spatial data infrastructures, the networks of standards, repositories, and governance frameworks that underpin ocean data sharing, can be aligned with the principles of open science and with the FAIR guidelines, which hold that research data should be findable, accessible, interoperable, and reusable. The central claim is deceptively simple: sustainable ocean management is only as good as the knowledge systems that feed it, and those systems are currently too disjointed to support the decisions the ocean urgently needs.</p>
<p>The timing of this argument is not accidental. The United Nations Decade of Ocean Science for Sustainable Development has entered its second half, and the ambitions set out in 2021 are colliding with the practical realities of data governance. The Kunming-Montreal Global Biodiversity Framework commits nations to protecting thirty percent of land and sea by 2030, the high seas treaty known as the Biodiversity Beyond National Jurisdiction agreement is moving toward implementation, and marine spatial planning initiatives are expanding across every continent. Each of these commitments depends on the ability to ask hard, quantitative questions: Where are the biodiversity hotspots? How do shipping lanes overlap with whale migration corridors? Which seafloor habitats will be most resilient as waters warm and acidify? Answering them requires integrating physical oceanography, biology, geology, human-use data, and socioeconomic information at resolutions and accuracies that no single institution can produce alone.</p>
<p>Marine spatial data infrastructures, often abbreviated as MSDIs, emerged over the past two decades as a response to exactly this integration problem. Modeled in part on terrestrial spatial data infrastructures developed for land management, MSDIs provide the technical scaffolding for storing, cataloging, and serving geospatial ocean data. They define metadata standards that describe where a measurement was taken, when, by what instrument, and under what quality-control procedures. They establish web services that allow a map of coral reef extent in one national database to be layered seamlessly onto shipping density data held by an international maritime body. In principle, an MSDI lets a marine planner in a coastal ministry assemble a complete picture of their waters without ever downloading a raw file. In practice, the authors contend, the promise remains unevenly realized.</p>
<p>The technical barriers are real but solvable, and the article is refreshingly specific about them. Ocean data arrives in a bewildering array of formats: netCDF files from oceanographic models, Darwin Core archives from biodiversity surveys, Shapefiles and GeoJSON from habitat mapping, and proprietary formats from acoustic and optical sensors. Vocabulary mismatches compound the format problem, as one agency&#8217;s benthic habitat classification may bear little resemblance to another&#8217;s even when describing the same seafloor. Semantic interoperability, the ability of machines to understand not just that two datasets exist but that they describe comparable phenomena, demands shared ontologies and controlled vocabularies such as those maintained by the community behind the NERC Vocabulary Server and the Marine Regions gazetteer. FAIR alignment pushes these requirements further, insisting that data carry persistent identifiers, that metadata be rich enough for independent reuse, and that licenses clearly state what others may do with the material.</p>
<p>What elevates the article beyond a technical audit is its insistence that infrastructure is inseparable from culture and equity. Open science, the authors emphasize, is not merely the removal of paywalls from publications. It is a systemic commitment to transparency across the entire research lifecycle, from preregistered sampling designs to openly licensed datasets to reproducible analysis code. Applied to the ocean, this commitment carries a justice dimension that is easy to overlook from well-funded laboratories in the Global North. Much of the world&#8217;s marine data is collected in the waters of developing nations and small island states, yet the analytical capacity to exploit it is concentrated elsewhere. A genuinely aligned knowledge system would ensure that coastal communities who steward coral reefs, mangroves, and fisheries can access, understand, and contribute to the data describing their own seascapes, rather than serving as passive subjects of extraction by international research programs.</p>
<p>The authors sketch what this alignment looks like in operational terms. National and regional MSDIs would adopt FAIR-compliant repositories with persistent identifiers for every dataset and sample. Metadata would follow internationally recognized standards such as ISO 19115 for geospatial information, supplemented by community schemas for biological occurrences. Application programming interfaces, built on open protocols like OGC standards and the SPARQL query language for linked data, would allow researchers and decision-makers to compose datasets on the fly rather than negotiating bilateral data-sharing agreements that can take years. Crucially, the vision includes provenance tracking, so that a sea surface temperature anomaly used in a fisheries closure decision can be traced back through every processing step to the original instrument deployment. In an era when contested science can stall policy for a decade, that traceability is not bureaucratic decoration; it is the foundation of trust.</p>
<p>The article also confronts the hard economics of open infrastructure. Repositories cost money to run, data curation is skilled labor, and long-term stewardship of ocean observations requires funding models that outlast individual grants. The authors point to the tension between mandates for immediate open data and the legitimate needs of researchers to publish from their own collections, arguing for community norms that balance openness with recognition. They highlight the role of coordinated bodies, including the Intergovernmental Oceanographic Commission&#8217;s International Oceanographic Data and Information Exchange program and the emerging Ocean Data and Information System, as the connective tissue that can harmonize national efforts without imposing one-size-fits-all solutions on institutions with wildly different capacities.</p>
<p>Perhaps the most compelling thread in the analysis concerns artificial intelligence and the coming wave of machine-driven discovery. Foundation models trained on ocean observations, digital twins that simulate entire ocean basins, and automated anomaly detection for illegal fishing all presuppose data that machines can read, validate, and combine at scale. FAIR infrastructure designed for human users a decade ago is not automatically fit for this purpose. Machine-actionable metadata, semantically annotated datasets, and interoperable services are the raw substrate on which the next generation of ocean intelligence will be built. The authors make clear that this is not a distant hypothetical; it is happening now, and knowledge infrastructures that fail to adapt risk becoming irrelevant bottlenecks in an otherwise accelerating field.</p>
<p>The stakes could hardly be higher. The ocean regulates the planet&#8217;s climate, feeds billions of people, and harbors the largest reservoir of life on Earth, yet it is warming, acidifying, deoxygenating, and losing biodiversity at rates that outpace many models. The article&#8217;s conclusion is ultimately an optimistic one: the pieces of a global, equitable, and technically rigorous ocean knowledge system already exist in scattered form. Standards bodies, data centers, and open science movements have each built parts of the puzzle. What remains, the authors argue, is deliberate alignment, the patient diplomatic and technical work of making these components interoperable, FAIR-compliant, and responsive to the communities who depend on ocean knowledge most. If that work succeeds, the invisible ocean becomes visible not just to satellites and supercomputers, but to every planner, scientist, and citizen with a stake in its future.</p>
<p><strong>Subject of Research:</strong> Integration of marine spatial data infrastructures with FAIR principles and open science for sustainable ocean knowledge systems</p>
<p><strong>Article Title:</strong> Aligning Marine Spatial Data Infrastructures and Open Science for FAIR and sustainable ocean knowledge systems</p>
<p><strong>Article References:</strong> Aligning Marine Spatial Data Infrastructures and Open Science for FAIR and sustainable ocean knowledge systems. (n.d.). <a href="https://doi.org/10.1038/s44183-026-00246-6" rel="noopener noreferrer">https://doi.org/10.1038/s44183-026-00246-6</a></p>
<p><strong>Image Credits:</strong> AI Generated</p>
<p><strong>DOI:</strong> <a href="https://doi.org/10.1038/s44183-026-00246-6" rel="noopener noreferrer">10.1038/s44183-026-00246-6</a></p>
<p><strong>Keywords:</strong> marine spatial data infrastructure, FAIR principles, open science, ocean sustainability, ocean data governance, semantic interoperability, marine spatial planning, ocean observations, data infrastructure, biodiversity data, ocean decade, digital ocean</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">197816</post-id>	</item>
		<item>
		<title>Ontologies Could Be the Missing Link That Finally Makes Big Data Work in Healthcare</title>
		<link>https://scienmag.com/ontologies-could-be-the-missing-link-that-finally-makes-big-data-work-in-healthcare/</link>
		
		<dc:creator><![CDATA[Denise Maddox]]></dc:creator>
		<pubDate>Sat, 12 Sep 2026 15:29:41 +0000</pubDate>
				<category><![CDATA[Technology and Engineering]]></category>
		<category><![CDATA[biomedical knowledge modeling]]></category>
		<category><![CDATA[biomedical research database management]]></category>
		<category><![CDATA[clinical data interoperability]]></category>
		<category><![CDATA[clinical decision support]]></category>
		<category><![CDATA[electronic health record data organization]]></category>
		<category><![CDATA[electronic health records]]></category>
		<category><![CDATA[Hadoop]]></category>
		<category><![CDATA[healthcare big data]]></category>
		<category><![CDATA[healthcare data integration]]></category>
		<category><![CDATA[healthcare data quality issues]]></category>
		<category><![CDATA[IoT healthcare]]></category>
		<category><![CDATA[Kafka]]></category>
		<category><![CDATA[knowledge graphs]]></category>
		<category><![CDATA[medical imaging data structuring]]></category>
		<category><![CDATA[medical information standardization]]></category>
		<category><![CDATA[ontologies]]></category>
		<category><![CDATA[ontology-based data access]]></category>
		<category><![CDATA[ontology-driven semantic data management]]></category>
		<category><![CDATA[semantic annotation]]></category>
		<category><![CDATA[semantic fragmentation in healthcare]]></category>
		<category><![CDATA[semantic interoperability]]></category>
		<category><![CDATA[solutions for healthcare data swamps]]></category>
		<category><![CDATA[Spark]]></category>
		<category><![CDATA[wearable sensor data analysis]]></category>
		<guid isPermaLink="false">https://scienmag.com/?p=195911</guid>

					<description><![CDATA[A systematic review in Knowledge and Information Systems shows that ontology-driven semantic data management can align fragmented healthcare standards, enable scalable real-time analytics and strengthen clinical decision support across big data platforms.]]></description>
										<content:encoded><![CDATA[<p>Modern medicine produces an extraordinary torrent of information. Electronic health records, medical imaging archives, wearable sensors and biomedical research databases now generate data on a scale that no single clinician, hospital or even national health system can meaningfully digest. A new systematic review published in Knowledge and Information Systems argues that the missing ingredient in turning this flood into useful insight is not more storage or faster processors, but a formal structure for meaning itself: ontology-driven semantic data management. The review, led by Ritesh Chandra of the Indian Institute of Information Technology Allahabad together with Sonali Agarwal, Navjot Singh and Sadhana Tiwari, maps out how ontologies, essentially formal, machine-readable models of domain knowledge, can rescue healthcare data lakes from descending into disorganized data swamps.</p>
<p>The core problem the authors identify is semantic fragmentation. Clinical information is recorded using a patchwork of competing standards such as ICD, SNOMED CT and HL7 FHIR, and these vocabularies do not align cleanly with one another. The same medical condition may be recorded differently across systems, an issue the review calls semantic inconsistency, and it directly undermines interoperability and the accuracy of large-scale analysis. On top of this come poor data quality, with missing or noisy entries in electronic health records and sensor streams, privacy risks inherent to sensitive patient records, and the sheer scalability demands posed by real-time intensive care units and the Internet of Things. Without a shared layer of meaning, the review warns, centralized repositories built to handle the volume, variety and velocity of big data risk devolving into repositories of noise.</p>
<p>Ontologies offer a solution by linking raw metadata to healthcare knowledge graphs, formal structures in which concepts such as diseases, drugs, symptoms and procedures are connected by defined relationships. This linkage enhances semantic interoperability, improves data discoverability, and enables expressive, domain-aware access to stored information. Rather than forcing every hospital to adopt identical data entry conventions, an ontology layer acts as a translation bridge: algorithms can reason about what a code in one system means in the vocabulary of another, aligning heterogeneous standards that would otherwise remain incompatible. The review documents how this approach significantly improves query efficiency across distributed datasets and enables scalable, real-time analytics for continuous patient monitoring.</p>
<p>To bring order to a sprawling literature, the researchers formulated key research questions and conducted a structured search across major academic databases, then classified the resulting studies into six categories of ontology-driven healthcare analytics. These are ontology-driven integration frameworks; semantic modeling for metadata enrichment; ontology-based data access, known in the field as OBDA; basic semantic data management; ontology-based reasoning for decision support; and semantic annotation for unstructured data. The classification serves as both a map of the current research landscape and a practical taxonomy that hospital technology teams and vendors can use to position their own tools and projects.</p>
<p>Several of these categories are already producing concrete clinical results. In the integration domain, studies demonstrate that ontological models of healthcare data built through metamodeling techniques and natural language processing can unify heterogeneous databases within a single domain, allowing previously siloed systems to exchange meaning rather than just files. Semantic annotation has become particularly powerful in recent years: tools such as the MedCAT clinical natural language processing toolkit map free-text clinical notes onto ontology concepts, while other work applies ontology-driven, weakly supervised models to identify rare diseases buried in clinical narratives. Entity-linking benchmarks for SNOMED CT, such as SNOBERT, show that machine learning can now attach precise terminology codes to messy clinician prose at scale, a task that once required painstaking manual coding.</p>
<p>Ontology-based data access deserves special attention because it changes who can query medical information. In an OBDA architecture, the user poses questions in high-level ontological terms, and the system translates them automatically into queries over underlying relational or NoSQL data stores. The review highlights systems such as ATHENA, which allowed natural language querying over relational databases, and Pathling, which performs analytics directly on HL7 FHIR data. Benchmarking efforts like LUBM4OBDA are now measuring how well these systems handle inference and large-scale query answering. The practical payoff is that clinicians and researchers can ask domain-meaningful questions without mastering the schema quirks of dozens of backend databases, a democratization of information access that the review identifies as a key trend.</p>
<p>The third pillar, ontology-based reasoning for decision support, is where semantics meets patient care most directly. Clinical decision support systems built on reasoning engines can infer context-aware conclusions from patient data, for example flagging prescribing errors, recommending treatment pathways or predicting cardiovascular risk. The review cites studies such as OnTopharma, an ontology-based system shown to reduce medication prescribing errors, and personalized decision support systems for complex chronic patients. Rule languages like SWRL allow medical knowledge to be encoded as executable logic, and the authors&#8217; own prior work demonstrates ontology-driven diagnosis of vector-borne diseases and explainable artificial intelligence for liver disease diagnosis. Fuzzy and probabilistic extensions of ontology reasoning, which handle uncertainty explicitly, are highlighted as an important frontier given how much clinical knowledge is inherently imprecise.</p>
<p>Crucially, the review examines how ontology technologies integrate with the industrial machinery of big data: the frameworks of Hadoop, Spark and Kafka. Kafka&#8217;s streaming pipelines can feed real-time sensor and ICU data through ontology-based complex event processing, an approach the authors have explored in their OCEP framework for healthcare decision support. Spark provides distributed in-memory computation for reasoning-heavy workloads, while Hadoop&#8217;s storage layer underpins batch processing of longitudinal patient records. Studies of ontology-based IoT healthcare systems, including cardiac e-health models built on the SAREF4health IoT standard, show that semantic models can ride on top of these scalable platforms without sacrificing real-time responsiveness. The combined stack delivers scalable and intelligent analytics, the review concludes, from population-level dashboards to bedside monitoring.</p>
<p>None of this is frictionless, and the review is candid about the challenges. Reasoning over expressive ontologies is computationally expensive, and performance degrades as knowledge bases grow; large-scale deployment remains an open gap. Building and maintaining ontologies requires specialized expertise, and quality assurance of the ontologies themselves is a recognized problem, with dedicated big-data approaches proposed for auditing biomedical ontologies. Privacy-aware semantic modeling is identified as a key research gap, since richer knowledge graphs can paradoxically increase re-identification risk, prompting proposals that combine ontologies with access control models, provenance management and blockchain technology. The authors also flag organizational obstacles: healthcare institutions must invest in governance to prevent even semantically enriched data lakes from lapsing into swamps.</p>
<p>The trajectory, however, points clearly upward. The review identifies artificial intelligence, machine learning, the Internet of Things and real-time analytics as the dominant emerging trends reshaping ontology-driven healthcare analytics, with large language models now being harnessed to automate ontology engineering tasks, from generating competency questions to mapping indicators onto knowledge graphs. Hybrid systems that couple neural networks with symbolic knowledge graphs are attracting particular interest for interpretable medical AI. For each of its six categories, the review catalogs recent techniques, representative case studies, technical and organizational hurdles, and future directions, aiming to guide the development of sustainable, interoperable and high-performance healthcare data ecosystems. In a field drowning in its own data, the message is that meaning, not just capacity, is the resource that medicine must now engineer.</p>
<p><strong>Subject of Research:</strong> A systematic review of ontology-driven big data analytics approaches, tools and applications in healthcare</p>
<p><strong>Article Title:</strong> A review of ontology-driven big data analytics in healthcare: challenges, tools, and applications</p>
<p><strong>Article References:</strong> Chandra, R., Agarwal, S., Singh, N., &amp; Tiwari, S. (2026). A review of ontology-driven big data analytics in healthcare: challenges, tools, and applications. <em>Knowledge and Information Systems, 68</em>(1), Article 258. <a href="https://doi.org/10.1007/s10115-026-02864-5" rel="noopener noreferrer">https://doi.org/10.1007/s10115-026-02864-5</a></p>
<p><strong>Image Credits:</strong> AI Generated</p>
<p><strong>DOI:</strong> <a href="https://doi.org/10.1007/s10115-026-02864-5" rel="noopener noreferrer">10.1007/s10115-026-02864-5</a></p>
<p><strong>Keywords:</strong> ontologies, healthcare big data, semantic interoperability, knowledge graphs, ontology-based data access, clinical decision support, electronic health records, Hadoop, Spark, Kafka, IoT healthcare, semantic annotation</p>
]]></content:encoded>
					
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">195911</post-id>	</item>
	</channel>
</rss>
