Automated Generation of SADI Web Services for Clinical Intelligence using Ruled-Based Semantic Mappings.
Notice bibliographique
Résumé
We present a framework that automates the generation of SADI semantic web services from declarative service descriptions and semantic mappings to relational data. Mappings are specified in a Datalog sublanguage of Positional-Slotted Object-Applicative (PSOA) RuleML. We outline a novel methodology, a system architecture, and a prototype implementation for service generation. A proof-of-concept implementation and preliminary evaluation of the approach was conducted by generating a set of SADI services over a database representing a fragment of a hospital research data warehouse. These automatically generated fully functional services are used to answer simple SPARQL queries. Infection control practitioners involved in surveillance for Hospital-Acquired Infections (HAI) need to access multiple sources of clinical data in relational databases. Ad-hoc retrieval of information from these databases requires knowledge of query languages like SQL, albeit surveillance and decision making would be more efficient if practitioners could retrieve relevant data without IT support. Semantic Querying facilitates self-service querying by non-technical users as described recently in HAIKU [1], where SADI Semantic Web services were deployed on relational databases to provide access to HAI-related data from The Ottawa Hospital (TOH) Data Warehouse (DW). While the method successfully enables domain experts (e.g. surveillance practitioners) to semantically query relational data using terminologies from domain specific ontologies, it requires prior scripting of Java code and SQL queries to operationalize the SADI Web services. This is labor-intensive, error-prone, and mandates the availability and involvement of surveillance practitioners to consult with the IT personnel during service creation. As such, the process is a good target for automation. Expanding on our previous work [2], we present an architecture designed to support semantic query rewriting Fig. 1, where SADI Semantic Web service code is generated automatically from declarative input and output descriptions, and a semantic mapping of the source data in PSOA RuleML [3]. Our implementation of the architecture facilitates Web service generation without human intervention and end users are able to run queries executing the generated services using SADI query engines, such as SHARE and HYDRA [1] . Fig. 1: Architecture supporting the automation of SADI Semantic Web service generation The service generation process relies on four distinct modules working together: a Semantic Mapping Module representing the correspondence of a DB schema to a domain ontology, a Service Description Module where service inputs and outputs are formalized, an SQL-template Query Generator Module, and a Service Generator Module to output executable Java code for a SADI web service. Generated services are then indexed in a SADI registry. In testing the query engine, HYDRA was able to discover the appropriate services in the registry and execute queries over the data. Based on a list of previously identified target use cases [1], our system is being further evaluated for its utilty in provisioning Semantic Querying to access HAI-related data from TOH DW. A list of frequently asked questions 5 is available for interested readers.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction distillée sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,001 | 0,000 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,000 | 0,000 |
| Bibliométrie | 0,000 | 0,000 |
| Études des sciences et des technologies | 0,000 | 0,000 |
| Communication savante | 0,000 | 0,000 |
| Science ouverte | 0,001 | 0,000 |
| Intégrité de la recherche | 0,000 | 0,000 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,000 | 0,000 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule tête enseignante, pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».