Evidence map›Paper›PMID 24993546›Full record

ArticleJournal of the American Medical Informatics Association : JAMIA

Lessons learned in detailed clinical modeling at Intermountain Healthcare.

Thomas A Oniki, Joseph F Coyle, Craig G Parker, Stanley M Huff

Open access · bronzeAbstract read
In one paragraph

Article in Journal of the American Medical Informatics Association : JAMIA. The graph could read no effect estimate from its abstract, so it casts no vote on the map. Cited by 12 papers, 1 of them a synthesis that pooled it.

0numbers the graph read from it
0cells of the map it votes in
12citing papers in PubMed, 1 pooled it
1.4field-weighted citation impact, top 19% of its field
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

12 citing papers in PubMed, 1 synthesis or guideline pooled it, 26 citations in OpenAlex.

  1. Pooled it
  2. Article
  3. Article
  4. Article
  5. Article
  6. Evaluation of clinical information modeling tools.Journal of the American Medical Informatics Association : JAMIA · 2016
    Article
  7. An information model for computable cancer phenotypes.BMC medical informatics and decision making · 2016
    Article
  8. Clinical element models in the SHARPn consortium.Journal of the American Medical Informatics Association : JAMIA · 2016
    Article
  9. Article
  10. Article
  11. Automatic Extraction and Post-coordination of Spatial Relations in Consumer Language.AMIA ... Annual Symposium proceedings. AMIA Symposium · 2015
    Article
  12. Article
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

4 authors at 2 institutions in 1 country.

Thomas A OnikiDepartment of Medical Informatics, Intermountain Healthcare, Salt Lake City, Utah, USA.
Joseph F CoyleDepartment of Medical Informatics, Intermountain Healthcare, Salt Lake City, Utah, USA.
Craig G ParkerDepartment of Medical Informatics, Intermountain Healthcare, Salt Lake City, Utah, USA.
Stanley M HuffDepartment of Medical Informatics, Intermountain Healthcare, Salt Lake City, Utah, USA Department of Biomedical Informatics, University of Utah, Salt Lake City, Utah, USA.
Intermountain Healthcare · USUniversity of Utah · US

Funding

NCATS NIH HHS 90TR002
6 · The paper itself

Abstract

BACKGROUND AND

objectiveIntermountain Healthcare has a long history of using coded terminology and detailed clinical models (DCMs) to govern storage of clinical data to facilitate decision support and semantic interoperability. The latest iteration of DCMs at Intermountain is called the clinical element model (CEM). We describe the lessons learned from our CEM efforts with regard to subjective decisions a modeler frequently needs to make in creating a CEM. We present insights and guidelines, but also describe situations in which use cases conflict with the guidelines. We propose strategies that can help reconcile the conflicts. The hope is that these lessons will be helpful to others who are developing and maintaining DCMs in order to promote sharing and interoperability.

methodsWe have used the Clinical Element Modeling Language (CEML) to author approximately 5000 CEMs.

resultsBased on our experience, we have formulated guidelines to lead our modelers through the subjective decisions they need to make when authoring models. Reported here are guidelines regarding precoordination/postcoordination, dividing content between the model and the terminology, modeling logical attributes, and creating iso-semantic models. We place our lessons in context, exploring the potential benefits of an implementation layer, an iso-semantic modeling framework, and ontologic technologies.

conclusionsWe assert that detailed clinical models can advance interoperability and sharing, and that our guidelines, an implementation layer, and an iso-semantic framework will support our progress toward that goal.

Indexed as

Clinical CodingDecision Support TechniquesProgramming LanguagesVocabulary, ControlledElectronic Health RecordsHealth Information SystemsHumansMedical Record LinkageMedical Records Systems, ComputerizedSemanticsSystems IntegrationUtahHealth Information Systems/StandardsInformation Storage and RetrievalMedical Records Systems, Computerized/StandardsSemanticsVocabulary, Controlled

Identifiers

PMID24993546
PMCPMC4215059
OpenAlexW2110244395

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.