Evidence map›Paper›PMID 32940707›Full record

ArticleJournal of the American Medical Informatics Association : JAMIA2020

Using UMLS for electronic health data standardization and database design.

Andrew P Reimer, Alex Milinovich

Abstract read
In one paragraph

Article in Journal of the American Medical Informatics Association : JAMIA, 2020. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Cited by 15 papers.

0numbers the graph read from it
0cells of the map it votes in
15citing papers in PubMed
–field-weighted citation impact
1 · What the graph read from it

What it found

Each row is one number read from the abstract, on the scale the paper reported it, with its interval. Left of the dashed line favours the treatment, right favours the comparator. Under each row is the sentence it came from. New to these charts? A ten-minute tutorial.

The abstract states no effect estimate the extractor could read, or names no intervention and outcome on the map, so this paper lights no cell and moves no belief. It is still indexed, cited and linked below.

2 · The registry

The trial behind it

Trials whose registry record cites this paper, or whose number appears in the abstract. A trial that started after this paper was published is citing it as background, not reporting it.

Neither the registry nor the abstract names a trial number. If this is a trial report, that itself is worth knowing.

3 · Its place in the literature

Who cites it

15 citing papers in PubMed.

  1. Article
  2. Article
  3. Article
  4. Article
  5. Article
  6. Article
  7. Clinical Data Warehousing: A Scoping Review.Journal of the Society for Clinical Data Management · 2024
    Article
  8. Nursing Informatics' Contribution to One Health.Yearbook of medical informatics · 2023
    Article
  9. Article
  10. A GCN-based approach to uncover misaligned synonymous terms in the UMLS Metathesaurus.AMIA ... Annual Symposium proceedings. AMIA Symposium · 2023
    Article
  11. Observational
  12. Article
  13. Article
  14. Article
  15. Review
4 · The record

Corrections and comments

PubMed lists nothing against this paper. Absence here is not a guarantee, only a check that was made.

5 · Who and what money

Authors and funding

2 authors.

Andrew P ReimerFrances Payne Bolton School of Nursing, Case Western Reserve University, Cleveland, Ohio,USA.
Alex MilinovichDepartment of Quantitative Health Sciences, Cleveland Clinic, Cleveland, Ohio,USA.

Funding

Identifying Electronic Phenotypes associated with Patient Health Outcomes of Interhospital Transfer PatientsR15NR017792 · NINR · CASE WESTERN RESERVE UNIVERSITY · PI REIMER, ANDREW PAUL · 2018 to 2018
$477k
NINR NIH HHS R15 NR017792
6 · The paper itself

Abstract

objectivePatients that undergo medical transfer represent 1 patient population that remains infrequently studied due to challenges in aggregating data across multiple domains and sources that are necessary to capture the entire episode of patient care. To facilitate access to and secondary use of transport patient data, we developed the Transport Data Repository that combines data from 3 separate domains and many sources within our health system.

methodsThe repository is a relational database anchored by the Unified Medical Language System unique concept identifiers to integrate, map, and standardize the data into a common data model. Primary data domains included sending and receiving hospital encounters, medical transport record, and custom hospital transport log data. A 4-step mapping process was developed: 1) automatic source code match, 2) exact text match, 3) fuzzy matching, and 4) manual matching.

results431 090 total mappings were generated in the Transport Data Repository, consisting of 69 010 unique concepts with 77% of the data being mapped automatically. Transport Source Data yielded significantly lower mapping results with only 8% of data entities automatically mapped and a significant amount (43%) remaining unmapped. DISCUSSION: The multistep mapping process resulted in a majority of data been automatically mapped. Poor matching of transport medical record data is due to the third-party vendor data being generated and stored in a nonstandardized format.

conclusionThe multistep mapping process developed and implemented is necessary to normalize electronic health data from multiple domains and sources into a common data model to support secondary use of data.

Indexed as

Patient TransferUnified Medical Language SystemDatabases, FactualData ManagementElectronic Health RecordsHumansdata curationdata managementdata warehousing, transportation of patientselectronic data processing

Identifiers

PMID32940707
PMCPMC7647352

What OpenQuestion holds

Textmetadata
Read underepoch 390

Registered trials

None linked

Read under generation 80e0d062 · epoch 390. Bibliography from PubMed, PubMed Central and OpenAlex; grants from NIH RePORTER; trial links from ClinicalTrials.gov; estimates, votes and beliefs from the OpenQuestion graph.