1 / 7

Mapping CEMs to SHARPn Phenotyping Algorithms: Enhancing EHR Data Interoperability

This study presents a framework for mapping Clinical Event Models (CEMs) to SHARPn phenotyping algorithms, aiming to improve data interoperability across Electronic Health Records (EHRs). By establishing normalized and standardized data definitions, the framework supports the integration of text-derived and structured data into high-throughput processes. It emphasizes logical models that adapt to diverse physical implementations, detailing criteria for case selection and the temporality of data. This approach effectively addresses gaps in mapping algorithms, exemplified by medicinally managed diabetes, facilitating more accurate healthcare delivery.

minna
Download Presentation

Mapping CEMs to SHARPn Phenotyping Algorithms: Enhancing EHR Data Interoperability

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Mapping CEMs to SHARPn Phenotyping Algorithms Tom Oniki, Ph.D., Medical Informaticist, Intermountain Healthcare Hongfang Liu, Ph.D., SHARPn Data Normalization Team Leader, Mayo Clinic Susan Rea Welch, Ph.D., B.S.N., Informatics Research Fellow, Intermountain Healthcare

  2. Data Normalization

  3. Normalized, standardized data definitions Enable shared data across EHRs Enable use of text-derived and/or structured data Computable data input to high throughput processes Clinical conceptualization of data requirements Logical, not physical models: Flexible to physical implementations Optionality in contents used Why Map CEMs to Phenotyping Algorithms

  4. Specific EHR structure/content used Selection criteria of cases for input Temporality of data Non-computable algorithm input, as written Aggregations, transformations, expressions and functions on EHR data in algorithm input specs: Compute Body Mass Index from Height and Weight data MAX (BODY MASS INDEX) GLUCOSE RESULT not coincident with PREGNANCY Not Solved by CEM to Algorithm Data Mapping

  5. Snippet of Medicinally Managed Diabetes Algorithm Patient meets AT LEAST One of the following Criteria: At least 2 face-to-faceoutpatient visits [1/1/09-12/31/10] with a diabetes ICD-9-CM code [list of codes given] OR Any medications ordered in [list of brand and generic medication names] OR At least 2 face-to-face outpatient visits with a capillary glucose result (glucometer) in the measurement period OR with an abnormal blood glucose or HbA1c result [thresholds given], not a glucose tolerance test and not part of a pregnancy screen.

More Related