Skip to main page content
U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.

Https

The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

Access keys NCBI Homepage MyNCBI Homepage Main Content Main Navigation
. 2016 Mar;23(2):248-56.
doi: 10.1093/jamia/ocv134. Epub 2015 Nov 13.

Clinical element models in the SHARPn consortium

Affiliations

Clinical element models in the SHARPn consortium

Thomas A Oniki et al. J Am Med Inform Assoc. 2016 Mar.

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.

PubMed Disclaimer

Figures

Figure 1:
Figure 1:
The Abstract Instance Model
Figure 2:
Figure 2:
An example CEM as a constraint on the Abstract Instance Model
Figure 3:
Figure 3:
An example of a CEM in CDL
Figure 4:
Figure 4:
The SHARPn Framework
Figure 5:
Figure 5:
An example of a SHARPn terminology mapping
Figure 6:
Figure 6:
A diagrammatic example of a secondary use constraint on a core model

References

    1. Coyle JF, Rossi Mori A, Huff SM . Standards for detailed clinical models as the basis for medical data exchange and decision support . Int J Med Inf 2003. ; 69 ( 2–3 ): 157 – 174 . - PubMed
    1. Coyle JF . The Clinical Element Model Detailed Clinical Models [dissertation] . Salt Lake City: : The University of Utah; ; 2013. .
    1. Huff SM, Rocha RA, Coyle JF, et al. . Integrating detailed clinical models into application development tools . Stud Health Technol Inform 2004. ; 107 ( Pt 2 ): 1058 – 1062 . - PubMed
    1. Goossen W, Goossen-Baremans A, van der Zel M . Detailed clinical models: a review . Healthc Inform Res 2010. ; 16 ( 4 ): 201 – 214 . - PMC - PubMed
    1. Parker CG, Rocha RA, Campbell JR, et al. . Detailed clinical models for sharable, executable guidelines . Stud Health Technol Inform 2004. ; 107 ( Pt 1 ): 145 – 148 . - PubMed

Publication types

MeSH terms