Clinical element models in the SHARPn consortium

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.

[1]  Stanley M. Huff,et al.  Standards for detailed clinical models as the basis for medical data exchange and decision support , 2003, Int. J. Medical Informatics.

[2]  Patrick B. Ryan,et al.  Development and evaluation of a common data model enabling active drug safety surveillance using disparate healthcare databases , 2010, J. Am. Medical Informatics Assoc..

[3]  Thomas Beale.  Archetypes and the EHR. , 2003, Studies in health technology and informatics.

[4]  Nicholas R. Hardiker,et al.  A Feasibility Study on Clinical Templates for the National Health Service in Scotland , 2007, MedInfo.

[5]  Carol Friedman,et al.  Towards a comprehensive medical language processing system: methods and issues , 1997, AMIA.

[6]  George Hripcsak,et al.  Natural language processing in an operational clinical information system , 1995, Natural Language Engineering.

[7]  Stanley M. Huff,et al.  Integrating Detailed Clinical Models Into Application Development Tools , 2004, MedInfo.

[8]  Stanley M. Huff,et al.  Lessons Learned in Detailed Clinical Modeling at Intermountain Healthcare , 2014, AMIA.

[9]  Sahana Murthy,et al.  Modeling and Executing Electronic Health Records Driven Phenotyping Algorithms using the NQF Quality Data Model and JBoss® Drools Engine , 2012, AMIA.

[10]  Bruce E. Bray,et al.  Architecture of a Federated Query Engine for Heterogeneous Resources , 2009, AMIA.

[11]  Ramkiran Gouripeddi,et al.  Federating clinical data from six pediatric hospitals: process and initial results from the PHIS+ Consortium. , 2011, AMIA ... Annual Symposium proceedings. AMIA Symposium.

[12]  David A. Ferrucci,et al.  Building an example application with the Unstructured Information Management Architecture , 2004, IBM Syst. J..

[13]  Seong-Woo Kim,et al.  Clinical Contents Model to Ensure Semantic Interoperability of Clinical Information , 2010 .

[14]  Stanley M. Huff,et al.  Detailed Clinical Models for Sharable, Executable Guidelines , 2004, MedInfo.

[15]  Cui Tao,et al.  Building a robust, scalable and standards-driven infrastructure for secondary use of EHR data: The SHARPn project , 2012, J. Biomed. Informatics.

[16]  Anneke T. M. Goossen-Baremans,et al.  Detailed Clinical Models: A Review , 2010, Healthcare informatics research.

[17]  Sunghwan Sohn,et al.  Mayo clinical Text Analysis and Knowledge Extraction System (cTAKES): architecture, component evaluation and applications , 2010, J. Am. Medical Informatics Assoc..

[18]  Cui Tao,et al.  Normalization and standardization of electronic health records for high-throughput phenotyping: the SHARPn consortium. , 2013, Journal of the American Medical Informatics Association : JAMIA.