Clinical element models in the SHARPn consortium

Thomas A. Oniki, Ning Zhuo, Calvin E. Beebe, Hongfang Liu, Joseph F. Coyle, Craig G. Parker, Harold Solbrig, Kyle Marchant, Vinod C. Kaggal, Christopher Chute, Stanley M. Huff

Research output: Contribution to journalArticle

Abstract

Objective: The objective of the Strategic Health IT Advanced Research Project area four (SHARPn) was to develop open-source tools that could be used for the normalization of electronic health record (EHR) data for secondary use-specifically, for high throughput phenotyping. We describe the role of Intermountain Healthcare's Clinical Element Models ([CEMs] Intermountain Healthcare Health Services, Inc, Salt Lake City, Utah) as normalization "targets" within the project. Materials and Methods: Intermountain's CEMs were either repurposed or created for the SHARPn project. A CEM describes "valid" structure and semantics for a particular kind of clinical data. CEMs are expressed in a computable syntax that can be compiled into implementation artifacts. The modeling team and SHARPn colleagues agilely gathered requirements and developed and refined models. Results: Twenty-eight "statement" models (analogous to "classes") and numerous "component" CEMs and their associated terminology were repurposed or developed to satisfy SHARPn high throughput phenotyping requirements. Model (structural) mappings and terminology (semantic) mappings were also created. Source data instances were normalized to CEM-conformant data and stored in CEM instance databases. A model browser and request site were built to facilitate the development. Discussion: The modeling efforts demonstrated the need to address context differences and granularity choices and highlighted the inevitability of iso-semantic models. The need for content expertise and "intelligent" content tooling was also underscored. We discuss scalability and sustainability expectations for a CEM-based approach and describe the place of CEMs relative to other current efforts. Conclusions: The SHARPn effort demonstrated the normalization and secondary use of EHR data. CEMs proved capable of capturing data originating from a variety of sources within the normalization pipeline and serving as suitable normalization targets.

Original languageEnglish (US)
Pages (from-to)248-256
Number of pages9
JournalJournal of the American Medical Informatics Association
Volume23
Issue number2
DOIs
StatePublished - Mar 1 2016
Externally publishedYes

Fingerprint

Semantics
Electronic Health Records
Terminology
Delivery of Health Care
Information Storage and Retrieval
Structural Models
Artifacts
Health Services
Databases
Health
Research

Keywords

  • Controlled
  • Electronic health records/standards
  • Health information systems/standards
  • Information storage and retrieval
  • Semantics
  • Vocabulary

ASJC Scopus subject areas

  • Health Informatics

Cite this

Oniki, T. A., Zhuo, N., Beebe, C. E., Liu, H., Coyle, J. F., Parker, C. G., ... Huff, S. M. (2016). Clinical element models in the SHARPn consortium. Journal of the American Medical Informatics Association, 23(2), 248-256. https://doi.org/10.1093/jamia/ocv134

Clinical element models in the SHARPn consortium. / Oniki, Thomas A.; Zhuo, Ning; Beebe, Calvin E.; Liu, Hongfang; Coyle, Joseph F.; Parker, Craig G.; Solbrig, Harold; Marchant, Kyle; Kaggal, Vinod C.; Chute, Christopher; Huff, Stanley M.

In: Journal of the American Medical Informatics Association, Vol. 23, No. 2, 01.03.2016, p. 248-256.

Research output: Contribution to journalArticle

Oniki, TA, Zhuo, N, Beebe, CE, Liu, H, Coyle, JF, Parker, CG, Solbrig, H, Marchant, K, Kaggal, VC, Chute, C & Huff, SM 2016, 'Clinical element models in the SHARPn consortium', Journal of the American Medical Informatics Association, vol. 23, no. 2, pp. 248-256. https://doi.org/10.1093/jamia/ocv134
Oniki, Thomas A. ; Zhuo, Ning ; Beebe, Calvin E. ; Liu, Hongfang ; Coyle, Joseph F. ; Parker, Craig G. ; Solbrig, Harold ; Marchant, Kyle ; Kaggal, Vinod C. ; Chute, Christopher ; Huff, Stanley M. / Clinical element models in the SHARPn consortium. In: Journal of the American Medical Informatics Association. 2016 ; Vol. 23, No. 2. pp. 248-256.
@article{a0f9d03439704f2cb638dbc4145dcf84,
title = "Clinical element models in the SHARPn consortium",
abstract = "Objective: The objective of the Strategic Health IT Advanced Research Project area four (SHARPn) was to develop open-source tools that could be used for the normalization of electronic health record (EHR) data for secondary use-specifically, for high throughput phenotyping. We describe the role of Intermountain Healthcare's Clinical Element Models ([CEMs] Intermountain Healthcare Health Services, Inc, Salt Lake City, Utah) as normalization {"}targets{"} within the project. Materials and Methods: Intermountain's CEMs were either repurposed or created for the SHARPn project. A CEM describes {"}valid{"} structure and semantics for a particular kind of clinical data. CEMs are expressed in a computable syntax that can be compiled into implementation artifacts. The modeling team and SHARPn colleagues agilely gathered requirements and developed and refined models. Results: Twenty-eight {"}statement{"} models (analogous to {"}classes{"}) and numerous {"}component{"} CEMs and their associated terminology were repurposed or developed to satisfy SHARPn high throughput phenotyping requirements. Model (structural) mappings and terminology (semantic) mappings were also created. Source data instances were normalized to CEM-conformant data and stored in CEM instance databases. A model browser and request site were built to facilitate the development. Discussion: The modeling efforts demonstrated the need to address context differences and granularity choices and highlighted the inevitability of iso-semantic models. The need for content expertise and {"}intelligent{"} content tooling was also underscored. We discuss scalability and sustainability expectations for a CEM-based approach and describe the place of CEMs relative to other current efforts. Conclusions: The SHARPn effort demonstrated the normalization and secondary use of EHR data. CEMs proved capable of capturing data originating from a variety of sources within the normalization pipeline and serving as suitable normalization targets.",
keywords = "Controlled, Electronic health records/standards, Health information systems/standards, Information storage and retrieval, Semantics, Vocabulary",
author = "Oniki, {Thomas A.} and Ning Zhuo and Beebe, {Calvin E.} and Hongfang Liu and Coyle, {Joseph F.} and Parker, {Craig G.} and Harold Solbrig and Kyle Marchant and Kaggal, {Vinod C.} and Christopher Chute and Huff, {Stanley M.}",
year = "2016",
month = "3",
day = "1",
doi = "10.1093/jamia/ocv134",
language = "English (US)",
volume = "23",
pages = "248--256",
journal = "Journal of the American Medical Informatics Association : JAMIA",
issn = "1067-5027",
publisher = "Oxford University Press",
number = "2",

}

TY - JOUR

T1 - Clinical element models in the SHARPn consortium

AU - Oniki, Thomas A.

AU - Zhuo, Ning

AU - Beebe, Calvin E.

AU - Liu, Hongfang

AU - Coyle, Joseph F.

AU - Parker, Craig G.

AU - Solbrig, Harold

AU - Marchant, Kyle

AU - Kaggal, Vinod C.

AU - Chute, Christopher

AU - Huff, Stanley M.

PY - 2016/3/1

Y1 - 2016/3/1

N2 - Objective: The objective of the Strategic Health IT Advanced Research Project area four (SHARPn) was to develop open-source tools that could be used for the normalization of electronic health record (EHR) data for secondary use-specifically, for high throughput phenotyping. We describe the role of Intermountain Healthcare's Clinical Element Models ([CEMs] Intermountain Healthcare Health Services, Inc, Salt Lake City, Utah) as normalization "targets" within the project. Materials and Methods: Intermountain's CEMs were either repurposed or created for the SHARPn project. A CEM describes "valid" structure and semantics for a particular kind of clinical data. CEMs are expressed in a computable syntax that can be compiled into implementation artifacts. The modeling team and SHARPn colleagues agilely gathered requirements and developed and refined models. Results: Twenty-eight "statement" models (analogous to "classes") and numerous "component" CEMs and their associated terminology were repurposed or developed to satisfy SHARPn high throughput phenotyping requirements. Model (structural) mappings and terminology (semantic) mappings were also created. Source data instances were normalized to CEM-conformant data and stored in CEM instance databases. A model browser and request site were built to facilitate the development. Discussion: The modeling efforts demonstrated the need to address context differences and granularity choices and highlighted the inevitability of iso-semantic models. The need for content expertise and "intelligent" content tooling was also underscored. We discuss scalability and sustainability expectations for a CEM-based approach and describe the place of CEMs relative to other current efforts. Conclusions: The SHARPn effort demonstrated the normalization and secondary use of EHR data. CEMs proved capable of capturing data originating from a variety of sources within the normalization pipeline and serving as suitable normalization targets.

AB - Objective: The objective of the Strategic Health IT Advanced Research Project area four (SHARPn) was to develop open-source tools that could be used for the normalization of electronic health record (EHR) data for secondary use-specifically, for high throughput phenotyping. We describe the role of Intermountain Healthcare's Clinical Element Models ([CEMs] Intermountain Healthcare Health Services, Inc, Salt Lake City, Utah) as normalization "targets" within the project. Materials and Methods: Intermountain's CEMs were either repurposed or created for the SHARPn project. A CEM describes "valid" structure and semantics for a particular kind of clinical data. CEMs are expressed in a computable syntax that can be compiled into implementation artifacts. The modeling team and SHARPn colleagues agilely gathered requirements and developed and refined models. Results: Twenty-eight "statement" models (analogous to "classes") and numerous "component" CEMs and their associated terminology were repurposed or developed to satisfy SHARPn high throughput phenotyping requirements. Model (structural) mappings and terminology (semantic) mappings were also created. Source data instances were normalized to CEM-conformant data and stored in CEM instance databases. A model browser and request site were built to facilitate the development. Discussion: The modeling efforts demonstrated the need to address context differences and granularity choices and highlighted the inevitability of iso-semantic models. The need for content expertise and "intelligent" content tooling was also underscored. We discuss scalability and sustainability expectations for a CEM-based approach and describe the place of CEMs relative to other current efforts. Conclusions: The SHARPn effort demonstrated the normalization and secondary use of EHR data. CEMs proved capable of capturing data originating from a variety of sources within the normalization pipeline and serving as suitable normalization targets.

KW - Controlled

KW - Electronic health records/standards

KW - Health information systems/standards

KW - Information storage and retrieval

KW - Semantics

KW - Vocabulary

UR - http://www.scopus.com/inward/record.url?scp=84963742240&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84963742240&partnerID=8YFLogxK

U2 - 10.1093/jamia/ocv134

DO - 10.1093/jamia/ocv134

M3 - Article

C2 - 26568604

AN - SCOPUS:84963742240

VL - 23

SP - 248

EP - 256

JO - Journal of the American Medical Informatics Association : JAMIA

JF - Journal of the American Medical Informatics Association : JAMIA

SN - 1067-5027

IS - 2

ER -