IDEAS home Printed from https://ideas.repec.org/a/plo/pone00/0110900.html
   My bibliography  Save this article

Defining Disease Phenotypes Using National Linked Electronic Health Records: A Case Study of Atrial Fibrillation

Author

Listed:
  • Katherine I Morley
  • Joshua Wallace
  • Spiros C Denaxas
  • Ross J Hunter
  • Riyaz S Patel
  • Pablo Perel
  • Anoop D Shah
  • Adam D Timmis
  • Richard J Schilling
  • Harry Hemingway

Abstract

Background: National electronic health records (EHR) are increasingly used for research but identifying disease cases is challenging due to differences in information captured between sources (e.g. primary and secondary care). Our objective was to provide a transparent, reproducible model for integrating these data using atrial fibrillation (AF), a chronic condition diagnosed and managed in multiple ways in different healthcare settings, as a case study. Methods: Potentially relevant codes for AF screening, diagnosis, and management were identified in four coding systems: Read (primary care diagnoses and procedures), British National Formulary (BNF; primary care prescriptions), ICD-10 (secondary care diagnoses) and OPCS-4 (secondary care procedures). From these we developed a phenotype algorithm via expert review and analysis of linked EHR data from 1998 to 2010 for a cohort of 2.14 million UK patients aged ≥30 years. The cohort was also used to evaluate the phenotype by examining associations between incident AF and known risk factors. Results: The phenotype algorithm incorporated 286 codes: 201 Read, 63 BNF, 18 ICD-10, and four OPCS-4. Incident AF diagnoses were recorded for 72,793 patients, but only 39.6% (N = 28,795) were recorded in primary care and secondary care. An additional 7,468 potential cases were inferred from data on treatment and pre-existing conditions. The proportion of cases identified from each source differed by diagnosis age; inferred diagnoses contributed a greater proportion of younger cases (≤60 years), while older patients (≥80 years) were mainly diagnosed in SC. Associations of risk factors (hypertension, myocardial infarction, heart failure) with incident AF defined using different EHR sources were comparable in magnitude to those from traditional consented cohorts. Conclusions: A single EHR source is not sufficient to identify all patients, nor will it provide a representative sample. Combining multiple data sources and integrating information on treatment and comorbid conditions can substantially improve case identification.

Suggested Citation

  • Katherine I Morley & Joshua Wallace & Spiros C Denaxas & Ross J Hunter & Riyaz S Patel & Pablo Perel & Anoop D Shah & Adam D Timmis & Richard J Schilling & Harry Hemingway, 2014. "Defining Disease Phenotypes Using National Linked Electronic Health Records: A Case Study of Atrial Fibrillation," PLOS ONE, Public Library of Science, vol. 9(11), pages 1-10, November.
  • Handle: RePEc:plo:pone00:0110900
    DOI: 10.1371/journal.pone.0110900
    as

    Download full text from publisher

    File URL: https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0110900
    Download Restriction: no

    File URL: https://journals.plos.org/plosone/article/file?id=10.1371/journal.pone.0110900&type=printable
    Download Restriction: no

    File URL: https://libkey.io/10.1371/journal.pone.0110900?utm_source=ideas
    LibKey link: if access is restricted and if your library uses this service, LibKey will redirect you to where you can use your library subscription to access this item
    ---><---

    More about this item

    Statistics

    Access and download statistics

    Corrections

    All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:plo:pone00:0110900. See general information about how to correct material in RePEc.

    If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.

    We have no bibliographic references for this item. You can help adding them by using this form .

    If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.

    For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: plosone (email available below). General contact details of provider: https://journals.plos.org/plosone/ .

    Please note that corrections may take a couple of weeks to filter through the various RePEc services.

    IDEAS is a RePEc service. RePEc uses bibliographic data supplied by the respective publishers.