Integrating Local Vocabulary into OMOP CDM: A Step-by-Step Tutorial

preprint OA: closed
📄 Open PDF Full text JSON View at publisher

Abstract

ABSTRACT Objectives This tutorial provides healthcare informatics researchers with a practical guide for integrating local vocabularies into the Observational Health Data Sciences and Informatics (OHDSI) Standardized Vocabularies, through the example of Korean Electronic Data Interchange (EDI) codes. Methods We present a step-by-step guide for integrating local vocabulary. The methodology includes four sequential stages: (1) comprehensive and continuous collection system for longitudinal EDI codes from November 2000 to May 2024, (2) mapping to OHDSI Standardized Vocabularies, (3) validation and integration through the OHDSI Community Contribution Pipeline, and (4) publication into the Athena, the official OHDSI vocabulary site. Results By following this tutorial, researchers can achieve integration of local vocabulary into the OHDSI Vocabularies. Of the total 620,642 EDI codes collected, we successfully integrated 437,807 codes (70.5%) into the OHDSI Vocabularies, with 376,111 (85.9%) of these integrated codes mapped to standard concepts. The integrated vocabulary passed all Community Contribution Pipeline requirements and was published in September 2024 on the official OHDSI vocabulary website. Conclusion This tutorial provides healthcare informatics researchers with practical guidance for vocabulary standardization, enabling local healthcare data integration into the OMOP CDM. The approach can be adapted for various local vocabularies, fostering international healthcare data interoperability.
Full text 25,599 characters · extracted from preprint-html · click to expand
Integrating Local Vocabulary into OMOP CDM: A Step-by-Step Tutorial | medRxiv /* */ /* */ <!-- <!-- /*! * yepnope1.5.4 * (c) WTFPL, GPLv2 */ (function(a,b,c){function d(a){return"[object Function]"==o.call(a)}function e(a){return"string"==typeof a}function f(){}function g(a){return!a||"loaded"==a||"complete"==a||"uninitialized"==a}function h(){var a=p.shift();q=1,a?a.t?m(function(){("c"==a.t?B.injectCss:B.injectJs)(a.s,0,a.a,a.x,a.e,1)},0):(a(),h()):q=0}function i(a,c,d,e,f,i,j){function k(b){if(!o&&g(l.readyState)&&(u.r=o=1,!q&&h(),l.onload=l.onreadystatechange=null,b)){"img"!=a&&m(function(){t.removeChild(l)},50);for(var d in y[c])y[c].hasOwnProperty(d)&&y[c][d].onload()}}var j=j||B.errorTimeout,l=b.createElement(a),o=0,r=0,u={t:d,s:c,e:f,a:i,x:j};1===y[c]&&(r=1,y[c]=[]),"object"==a?l.data=c:(l.src=c,l.type=a),l.width=l.height="0",l.onerror=l.onload=l.onreadystatechange=function(){k.call(this,r)},p.splice(e,0,u),"img"!=a&&(r||2===y[c]?(t.insertBefore(l,s?null:n),m(k,j)):y[c].push(l))}function j(a,b,c,d,f){return q=0,b=b||"j",e(a)?i("c"==b?v:u,a,b,this.i++,c,d,f):(p.splice(this.i++,0,a),1==p.length&&h()),this}function k(){var a=B;return a.loader={load:j,i:0},a}var l=b.documentElement,m=a.setTimeout,n=b.getElementsByTagName("script")[0],o={}.toString,p=[],q=0,r="MozAppearance"in l.style,s=r&&!!b.createRange().compareNode,t=s?l:n.parentNode,l=a.opera&&"[object Opera]"==o.call(a.opera),l=!!b.attachEvent&&!l,u=r?"object":l?"script":"img",v=l?"script":u,w=Array.isArray||function(a){return"[object Array]"==o.call(a)},x=[],y={},z={timeout:function(a,b){return b.length&&(a.timeout=b[0]),a}},A,B;B=function(a){function b(a){var a=a.split("!"),b=x.length,c=a.pop(),d=a.length,c={url:c,origUrl:c,prefixes:a},e,f,g;for(f=0;f<d;f++)g=a[f].split("="),(e=z[g.shift()])&&(c=e(c,g));for(f=0;f<b;f++)c=x[f](c);return c}function g(a,e,f,g,h){var i=b(a),j=i.autoCallback;i.url.split(".").pop().split("?").shift(),i.bypass||(e&&(e=d(e)?e:e[a]||e[g]||e[a.split("/").pop().split("?")[0]]),i.instead?i.instead(a,e,f,g,h):(y[i.url]?i.noexec=!0:y[i.url]=1,f.load(i.url,i.forceCSS||!i.forceJS&&"css"==i.url.split(".").pop().split("?").shift()?"c":c,i.noexec,i.attrs,i.timeout),(d(e)||d(j))&&f.load(function(){k(),e&&e(i.origUrl,h,g),j&&j(i.origUrl,h,g),y[i.url]=2})))}function h(a,b){function c(a,c){if(a){if(e(a))c||(j=function(){var a=[].slice.call(arguments);k.apply(this,a),l()}),g(a,j,b,0,h);else if(Object(a)===a)for(n in m=function(){var b=0,c;for(c in a)a.hasOwnProperty(c)&&b++;return b}(),a)a.hasOwnProperty(n)&&(!c&&!--m&&(d(j)?j=function(){var a=[].slice.call(arguments);k.apply(this,a),l()}:j[n]=function(a){return function(){var b=[].slice.call(arguments);a&&a.apply(this,b),l()}}(k[n])),g(a[n],j,b,n,h))}else!c&&l()}var h=!!a.test,i=a.load||a.both,j=a.callback||f,k=j,l=a.complete||f,m,n;c(h?a.yep:a.nope,!!i),i&&c(i)}var i,j,l=this.yepnope.loader;if(e(a))g(a,0,l,0);else if(w(a))for(i=0;i (function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0];var j=d.createElement(s);var dl=l!='dataLayer'?'&l='+l:'';j.src='//www.googletagmanager.com/gtm.js?id='+i+dl;j.type='text/javascript';j.async=true;f.parentNode.insertBefore(j,f);})(window,document,'script','dataLayer','GTM-P4HH5NV'); Skip to main content Home About Submit ALERTS / RSS Search for this keyword Advanced Search Integrating Local Vocabulary into OMOP CDM: A Step-by-Step Tutorial View ORCID Profile Yiju Park , Jinwoo Yoon , View ORCID Profile Aleh Zhuk , View ORCID Profile Anna Ostropolets , View ORCID Profile Seng Chan You doi: https://doi.org/10.1101/2025.05.07.25327200 Yiju Park 1 Department of Biomedical Systems Informatics, Yonsei University College of Medicine , Seoul, Republic of Korea 2 Institute for Innovation in Digital Healthcare, Yonsei University , Seoul, Republic of Korea BS Find this author on Google Scholar Find this author on PubMed Search for this author on this site ORCID record for Yiju Park Jinwoo Yoon 3 Business Insight powered by Science-technology, Concentrix Catalyst Korea , Seoul, Republic of Korea SA Find this author on Google Scholar Find this author on PubMed Search for this author on this site Aleh Zhuk 4 Odysseus , an EPAM Company, Cambridge, MA, USA MD Find this author on Google Scholar Find this author on PubMed Search for this author on this site ORCID record for Aleh Zhuk Anna Ostropolets 5 Observational Health Data Analytics, Janssen Research and Development , Titusville, NJ, USA 6 Department of Biomedical Informatics, Columbia University , NY, USA MD, PhD Find this author on Google Scholar Find this author on PubMed Search for this author on this site ORCID record for Anna Ostropolets Seng Chan You 1 Department of Biomedical Systems Informatics, Yonsei University College of Medicine , Seoul, Republic of Korea 2 Institute for Innovation in Digital Healthcare, Yonsei University , Seoul, Republic of Korea MD, PhD Find this author on Google Scholar Find this author on PubMed Search for this author on this site ORCID record for Seng Chan You For correspondence: chandryou{at}yuhs.ac Abstract Full Text Info/History Metrics Supplementary material Data/Code Preview PDF ABSTRACT Objectives This tutorial provides healthcare informatics researchers with a practical guide for integrating local vocabularies into the Observational Health Data Sciences and Informatics (OHDSI) Standardized Vocabularies, through the example of Korean Electronic Data Interchange (EDI) codes. Methods We present a step-by-step guide for integrating local vocabulary. The methodology includes four sequential stages: (1) comprehensive and continuous collection system for longitudinal EDI codes from November 2000 to May 2024, (2) mapping to OHDSI Standardized Vocabularies, (3) validation and integration through the OHDSI Community Contribution Pipeline, and (4) publication into the Athena, the official OHDSI vocabulary site. Results By following this tutorial, researchers can achieve integration of local vocabulary into the OHDSI Vocabularies. Of the total 620,642 EDI codes collected, we successfully integrated 437,807 codes (70.5%) into the OHDSI Vocabularies, with 376,111 (85.9%) of these integrated codes mapped to standard concepts. The integrated vocabulary passed all Community Contribution Pipeline requirements and was published in September 2024 on the official OHDSI vocabulary website. Conclusion This tutorial provides healthcare informatics researchers with practical guidance for vocabulary standardization, enabling local healthcare data integration into the OMOP CDM. The approach can be adapted for various local vocabularies, fostering international healthcare data interoperability. INTRODUCTION The standardization of healthcare data across different systems is essential for enabling large-scale observational research using real-world data[ 1 ]. The Observational Medical Outcomes Partnership Common Data Model (OMOP CDM), maintained by the Observational Health Data Sciences and Informatics (OHDSI), has emerged as a widely adopted framework for standardizing healthcare data structure and harmonizing its content[ 2 ]. As of 2024, over 540 data sources from 54 countries have been standardized to OMOP CDM[ 3 ]. A critical challenge in CDM adoption is incorporating local vocabularies used in different healthcare systems into the OHDSI Standardized Vocabularies, which is a mandatory reference standard in OMOP CDM. Vocabularies represent a collection of source terminologies, ontologies and vocabularies and crosswalks to reference standard terminologies. Integration of the local vocabularies into the OHDSI Vocabularies provides benefits for standardized and scalable research but involves multiple complex steps that require both technical expertise and domain knowledge. The OHDSI community recently introduced the Community Contribution Pipeline[ 4 ], establishing standardized guidelines for vocabulary integration. These guidelines primarily emphasize validation aspects while providing less detailed instruction on the comprehensive process from local vocabulary collection through mapping methodologies leaving such aspects to contributors. This presents additional challenges for newcomers seeking end-to-end guidance on vocabulary integration. Our research group previously integrated Korean EDI codes into the OMOP CDM in 2020, using available vocabulary at a single time point (October 2019)[ 5 ]. While this initial effort was valuable, it achieved limited mapping coverage and lacked a comprehensive approach for handling the longitudinal nature of vocabulary systems. This tutorial aims to provide a practical guide for integrating local vocabulary into the OHDSI Vocabularies using a semi-automated approach, with Korean Electronic Data Interchange (EDI) codes as a case example. We present a comprehensive step-by-step process covering the entire workflow from initial data collection, through data processing, mapping to international standard terminologies, evaluation and validation of terms to be loaded, to the final publication of terminology on vocabulary sites. The methodology presented here is designed to be accessible to beginners while providing sufficient detail for adaptation to other local vocabularies, thereby enhancing healthcare data interoperability across diverse healthcare systems. DESCRIPTION We developed a semi-automated pipeline consisting of four main components ( Figure 1 ). Our semi-automated approach automates data collection, processing, validation, and publication steps, while the integration with standard concepts requires manual expert review to ensure accuracy and semantic consistency. This combination of automation and expert judgment optimizes both efficiency and quality in vocabulary integration. Full details of all systems are given in the supplementary information. Download figure Open in new tab Figure 1. The overall process of EDI vocabulary integration into OMOP CDM Stage 1: Data Collection Data Source For this study, we collected EDI codes across all domains (Drug, Device, and Medical Service) from November 2000 to May 2024. In Korea, the EDI vocabulary system is the standard coding system for healthcare claims and electronic health records, provided by the Health Insurance Review & Assessment Service (HIRA). While widely used in Korea, EDI vocabulary presents several challenges for standardization efforts. First, HIRA releases updates to the EDI codes monthly for each domain separately, requiring frequent downloads and continuous maintenance. Additionally, the system lacks concept permanence, meaning expired codes can be reassigned to different concepts over time (re-used). The system also suffers from semantic inconsistencies, where the same codes may have different meanings depending on the context or the time period. These characteristics make the EDI vocabulary particularly challenging to harmonize with international standard terminologies. Data Processing Local vocabulary often requires comprehensive and continuous system approaches due to frequent updates, semantic inconsistencies, and longitudinal characteristics. Considering EDI’s longitudinal characteristics and code duplications, we implemented a comprehensive and continuous collection system, utilizing ‘SYNC’[ 6 ] (a modified version of previous ‘EdiToOmop’ package[ 5 , 7 ]) as a tool to track code updates and deprecations over the 23-year period. Figure 2 shows examples of how this system tracks code updates and deprecations. Our local vocabulary collection system performs four sequential steps ( Figure 3 ): Download figure Open in new tab Figure 2. Examples of EDI codes type Download figure Open in new tab Figure 3. The process of the semi-automated ‘SYNC’ package Scraping: Systematic extractsion of data from HIRA’s monthly announcements (Drug[ 8 ], Device, and Medical Service[ 9 ]) Yielding: Datasets were classified into four domains corresponding to the OMOP CDM domains - Device, Drug, Procedure, and Measurement. While the original EDI data only distinguished three domains (Device, Drug, and Medical Service), we further subdivided Medical Service codes into Procedure and Measurement domains based on their characteristics Nesting: Hierarchical structuring of domains (e.g., assigning Procedure/Proc Hierarchy concept class based on 5-digit numbers of EDI codes for Procedure domain classification) Converting: Automated English translation using a commercial machine translation API[ 10 ] The system is publicly available on GitHub[ 6 ] for transparency and reproducibility. Stage 2: Mapping to standard concepts Following the domain classification through our collection system, we mapped the EDI codes to standard OMOP concepts using the “Maps to” relationship. This mapping stage is the only step in our pipeline that requires significant manual effort, as it demands both clinical domain expertise and understanding of terminology standards. For each domain, we identified appropriate standard vocabularies: RxNorm and RxNorm Extension were used for Drug domain; SNOMED CT was selected for Device domain mapping; and both SNOMED CT and LOINC were utilized for Procedure and Measurement domains to ensure comprehensive coverage of clinical procedures and laboratory tests[ 11 ]. We prioritized the Drug and Device domains based on their importance in observational studies. To ensure accuracy and consistency, the experts followed OHDSI Korea Mapping guidelines[ 12 ]. Stage 3: Validation The Community Contribution Pipeline is the OHDSI’s standardized process for integrating new vocabularies into the OHDSI Vocabularies, ensuring quality and consistency through automated validation steps. The pipeline[ 4 ] performs five sequential stages. Table 1 provides detailed descriptions and function lists for each stage of the Community Contribution Pipeline. View this table: View inline View popup Download powerpoint Table 1. List of Community Contribution Pipeline Prerequisites (Environment Setup): Configuration of PostgreSQL database with three schemas – source, reference, and development – for systematic vocabulary management and vocabulary processing Load Stage (Vocabulary Loading): Integration of EDI codes collected through our comprehensive collection system and their mapped with standard concepts. This step also involves conversion of the source vocabulary structure into vocabulary-agnostic staging data structure QA/QC Part I (Quality Assessment): Initial quality checks focused on staging tables, including source data completeness, format validation, and data type conformity before integration into OMOP tables Generic Update (Vocabulary Integration): Integration of staged vocabularies into OMOP tables, establishing concept IDs and relationships QA/QC Part II (Final Validation): Validation for integrated vocabulary that combines automated quality checks for data integrity and change tracking, complemented by systematic manual review focusing on concept changes and their relationships Stage 4: Publication Following successful validation, we collaborated with the OHDSI Vocabulary Team[ 13 ] to address feedback and refine mappings. We submitted the outputs of our pipeline as the Community Contribution inputs, including ‘sources.edi_data’, ‘concept_stage’, ‘concept_synonym_stage’, ‘concept_relationship_stage’, and ‘concept_relationship_manual’ to receive final feedback. Additionally, to ensure code transparency and reproducibility, we committed the open-source code (SQL queries) used in the Community Contribution Pipeline process as issues to the OHDSI GitHub Vocabulary repository[ 14 ]. The integrated vocabulary that passed all requirements was published on Athena[ 15 ], the official OHDSI Vocabularies website. RESULT Building upon our previous work, which used only data from October 2019[ 5 ], the current study collected data spanning from 2000 to 2023 and mapped them with standard concepts following the mapping guidelines. Integration Coverage: Of the total 620,642 EDI codes collected from November 2000 to May 2024, we successfully integrated 437,807 codes (70.5%) into the OHDSI Vocabularies system with 376,111 standard concepts. Table 2 presents the domain-specific integration coverage, showing the proportion of collected codes that were successfully integrated. View this table: View inline View popup Download powerpoint Table 2. Domain-specific Integration Coverage of Korean EDI Codes Mapping Coverage: Table 3 presents a detailed comparison between previous and current code integration efforts in terms of mapping to standard concepts. Of the 437,807 integrated EDI codes, 376,111 (85.9%) were successfully mapped to standard concepts, compared to 0.5% (1,606/313,431) in previous attempt. View this table: View inline View popup Download powerpoint Table 3. Comparison of Mapping Coverage between Previous and Current Studies The integrated vocabulary passed all Community Contribution Pipeline requirements, including concept relationship consistency, domain classification accuracy, referential integrity validation, and terminology standard compliance. The final vocabulary was published in September 2024 on Athena [ 15 ], the official OHDSI vocabulary repository, enabling its use across the OHDSI network. DISCUSSION Our experience with integrating Korean EDI code demonstrates potential of local vocabulary standardization. By following the methodology outlined in this tutorial, we achieved an overall integration coverage of 70.5% (437,807/620,642) of all collected EDI codes, with 85.9% (376,111/437,807) of these integrated codes successfully mapped to standard concepts. This is a substantial improvement compared to the previous 0.5% (1,606/313,431) mapping coverage. While the overall integration and mapping coverage showed substantial improvement, challenges remain in specific domains. The particularly low coverage in the Measurement domain (2.5% integration, 8.1% mapping of integrated codes) warrants further discussion. This limitation stems from the high complexity and specificity of laboratory tests in the Korean healthcare system that often lack direct equivalents in international terminologies. To address these challenges, future work should focus on developing automated approaches to improve coverage while maintaining accuracy. The successful integration of Korean EDI codes demonstrates that local vocabularies with different structures, languages, and update patterns can be effectively incorporated into standardized data models. This approach contributes to the global OHDSI mission of generating reliable evidence from observational health data through international collaboration. Data Availability All data produced in the present work are contained in the manuscript CONFLICT OF INTEREST SCY reports being a chief executive officer of PHI Digital Healthcare; and grants from Daiichi Sankyo. Other authors declare that they have no competing interests. ACKNOWLEGMENT This work was supported by the National Research Foundation of Korea (NRF) grant funded by the Korea government (MSIT) (RS-2024-00341426). References 1. ↵ Biedermann P , Ong R , Davydov A , Orlova A , Solovyev P , Sun H , et al. Standardizing registry data to the OMOP Common Data Model: experience from three pulmonary hypertension databases . BMC Med Res Methodol . 2021 ; 21 ( 1 ): 238 . doi: 10.1186/s12874-021-01434-3 . OpenUrl CrossRef PubMed 2. ↵ Garza M , Del Fiol G , Tenenbaum J , Walden A , Zozus MN . Evaluating common data models for use with a longitudinal community registry . Journal of Biomedical Informatics . 2016 ; 64 : 333 – 41 . doi: 10.1016/j.jbi.2016.10.016 . OpenUrl CrossRef PubMed 3. ↵ Our journey 2024 . Available from: https://www.ohdsi.org/wp-content/uploads/2024/10/OurJourney2024.pdf . 4. ↵ Community contribution Pipeline . Available from: https://github.com/OHDSI/Vocabulary-v5.0/wiki/Community-contribution:-non%E2%80%90drug-vocabularies-p.II. 5. ↵ Seong Y , You SC , Ostropolets A , Rho Y , Park J , Cho J , et al. Incorporation of Korean Electronic Data Interchange Vocabulary into Observational Medical Outcomes Partnership Vocabulary . Healthc Inform Res . 2021 ; 27 ( 1 ): 29 – 38 . doi: 10.4258/hir.2021.27.1.29 . OpenUrl CrossRef 6. ↵ SYNC: Modified of EdiToOmop . Available from: https://github.com/dr-you-group/SYNC_EDItoOmopPackage . 7. ↵ EdiToOmop: Project to convert Korean EDI code to the OMOP vocabulary . Available from: https://github.com/OHDSI/EdiToOmop . 8. ↵ Data Source (Drug) . Available from: https://www.hira.or.kr/rc/insu/insuadtcrtr/InsuAdtCrtrList.do?pgmid=HIRAA030069000400&WT.gnb=%EB%B3%B4%ED%97%98%EC%9D%B8%EC%A0%95%EA%B8%B0%EC%A4%80. 9. ↵ Data Source (Devcie, Procedure and Measurement) . Available from: https://www.hira.or.kr/bbsDummy.do?pgmid=HIRAA030014050000&brdScnBltNo=4&brdBltNo=1676&pageIndex=1&pageIndex2=1 . 10. ↵ Cloud Translation API . Available from: https://cloud.google.com/translate/docs/reference/rest . 11. ↵ Reich C , Ostropolets A , Ryan P , Rijnbeek P , Schuemie M , Davydov A , et al. OHDSI Standardized Vocabularies—a large-scale centralized reference ontology for international data harmonization . Journal of the American Medical Informatics Association . 2024 ; 31 ( 3 ): 583 – 90 . doi: 10.1093/jamia/ocad247 . OpenUrl CrossRef PubMed 12. ↵ OHDSI-Korea Guideline: OHDSI-Korea ; 2023 [updated 2023/12/18/T05:47:35Z]. Available from: https://github.com/ohdsi-korea/OmopVocabularyKorea . 13. ↵ OHDSI Vocabulary Team: Observational Health Data Sciences and Informatics ; 2025 [updated 2025/02/04/T16:10:52Z]. Available from: https://github.com/OHDSI/Vocabulary-v5.0 . 14. ↵ Vocabulary-v5.0/EDI . Available from: https://github.com/OHDSI/Vocabulary-v5.0/tree/master/EDI . 15. ↵ Athena . Available from: https://athena.ohdsi.org/search-terms/start . View the discussion thread. Back to top Previous Next Posted May 08, 2025. Download PDF Supplementary Material Data/Code Email Thank you for your interest in spreading the word about medRxiv. NOTE: Your email address is requested solely to identify you as the sender of this article. Your Email * Your Name * Send To * Enter multiple addresses on separate lines or separate them with commas. You are going to email the following Integrating Local Vocabulary into OMOP CDM: A Step-by-Step Tutorial Message Subject (Your Name) has forwarded a page to you from medRxiv Message Body (Your Name) thought you would like to see this page from the medRxiv website. Your Personal Message CAPTCHA This question is for testing whether or not you are a human visitor and to prevent automated spam submissions. Share Integrating Local Vocabulary into OMOP CDM: A Step-by-Step Tutorial Yiju Park , Jinwoo Yoon , Aleh Zhuk , Anna Ostropolets , Seng Chan You medRxiv 2025.05.07.25327200; doi: https://doi.org/10.1101/2025.05.07.25327200 Share This Article: Copy Citation Tools Integrating Local Vocabulary into OMOP CDM: A Step-by-Step Tutorial Yiju Park , Jinwoo Yoon , Aleh Zhuk , Anna Ostropolets , Seng Chan You medRxiv 2025.05.07.25327200; doi: https://doi.org/10.1101/2025.05.07.25327200 Citation Manager Formats BibTeX Bookends EasyBib EndNote (tagged) EndNote 8 (xml) Medlars Mendeley Papers RefWorks Tagged Ref Manager RIS Zotero Tweet Widget Facebook Like Google Plus One Subject Area Health Informatics Subject Areas All Articles Addiction Medicine (567) Allergy and Immunology (863) Anesthesia (297) Cardiovascular Medicine (4412) Dentistry and Oral Medicine (443) Dermatology (380) Emergency Medicine (606) Endocrinology (including Diabetes Mellitus and Metabolic Disease) (1505) Epidemiology (15205) Forensic Medicine (30) Gastroenterology (1119) Genetic and Genomic Medicine (6575) Geriatric Medicine (666) Health Economics (994) Health Informatics (4511) Health Policy (1365) Health Systems and Quality Improvement (1608) Hematology (537) HIV/AIDS (1264) Infectious Diseases (except HIV/AIDS) (15904) Intensive Care and Critical Care Medicine (1103) Medical Education (620) Medical Ethics (144) Nephrology (666) Neurology (6573) Nursing (345) Nutrition (998) Obstetrics and Gynecology (1139) Occupational and Environmental Health (954) Oncology (3319) Ophthalmology (968) Orthopedics (369) Otolaryngology (420) Pain Medicine (435) Palliative Medicine (129) Pathology (662) Pediatrics (1689) Pharmacology and Therapeutics (691) Primary Care Research (710) Psychiatry and Clinical Psychology (5423) Public and Global Health (9205) Radiology and Imaging (2191) Rehabilitation Medicine and Physical Therapy (1367) Respiratory Medicine (1191) Rheumatology (593) Sexual and Reproductive Health (709) Sports Medicine (529) Surgery (709) Toxicology (99) Transplantation (288) Urology (265) (function(){function c(){var b=a.contentDocument||a.contentWindow.document;if(b){var d=b.createElement('script');d.innerHTML="window.__CF$cv$params={r:'9fecb6e138b8593a',t:'MTc3OTI5NDUwNQ=='};var a=document.createElement('script');a.src='/cdn-cgi/challenge-platform/scripts/jsd/main.js';document.getElementsByTagName('head')[0].appendChild(a);";b.getElementsByTagName('head')[0].appendChild(d)}}if(document.body){var a=document.createElement('iframe');a.height=1;a.width=1;a.style.position='absolute';a.style.top=0;a.style.left=0;a.style.border='none';a.style.visibility='hidden';document.body.appendChild(a);if('loading'!==document.readyState)c();else if(window.addEventListener)document.addEventListener('DOMContentLoaded',c);else{var e=document.onreadystatechange||function(){};document.onreadystatechange=function(b){e(b);'loading'!==document.readyState&&(document.onreadystatechange=e,c())}}}})();

Text is read by the "Ask this paper" AI Q&A widget below. Extraction quality varies by source — PMC NXML preserves structure cleanly, OA-HTML may include some navigation residue, and OA-PDF can have broken hyphenation. The publisher copy (via DOI) is the canonical version.

My notes (saved in your browser only)

Ask this paper AI returns verbatim quotes from the full text · source: preprint-html

Answers must be backed by verbatim quotes from this paper's full text. Hallucinated quotes are dropped automatically; if no verbatim passage answers the question, we say so. How this works

Citation neighborhood (no data yet)

We don't have any in-corpus citations linked to this paper yet. This is a recent paper (2025) — citers typically take a year or two to land, and the OpenAlex reference graph may still be filling in.

Source provenance

europepmc
last seen: 2026-05-20T01:45:00.602351+00:00