Share E-Book
Scan to open this page

Scan with your phone to open this page

Author: Andrew Nguyen

Rating 3.5 AI initial rating

Healthcare is the next frontier for data science. Using the latest in machine learning, deep learning, and natural language processing, you'll be able to solve healthcare's most pressing problems: reducing cost of care, ensuring patients get the best treatment, and increasing accessibility for the underserved. But first, you have to learn how to access and make sense of all that data. This book provides pragmatic and hands-on solutions for working with healthcare data, from data extraction to cleaning and harmonization to feature engineering. Author Andrew Nguyen covers specific ML and deep learning examples with a focus on producing high-quality data. You'll discover how graph technologies help you connect disparate data sources so you can solve healthcare's most challenging problems using advanced analytics. You'll learn: • Different types of healthcare data: electronic health records, clinical registries and trials, digital health tools, and claims data • The challenges of working with healthcare data, especially when trying to aggregate data from multiple sources • Current options for extracting structured data from clinical text • How to make trade-offs when using tools and frameworks for normalizing structured healthcare data • How to harmonize healthcare data using terminologies, ontologies, and mappings and crosswalks

AI Reading Assistant

Whole-book reading guide from stratified index samples; jump to passages in the text

AI guide
【One-Line Pitch】 A practical field guide to the messy reality of healthcare data—where it comes from, why it resists analysis, and how to extract, normalize, and harmonize it into something machine learning can actually use. Best for data scientists, engineers, and informatics professionals who already know the tools but need the domain vocabulary and judgment to work with clinical data responsibly. 【Book Arc】 - **Opening (~0%–10%)**: Frames healthcare as data science's next frontier and surveys the major source types—EHRs, registries, clinical trials, claims, and digital health—establishing why "real-world data" is fundamentally different from business data. - **Early (~10%–30%)**: Explains the mismatch between why healthcare data is collected (billing, reporting, care delivery) and what analysts want from it, using diagnosis-code examples to show how collection incentives distort the record. - **Early–Middle (~30%–45%)**: A technical baseline covering ACID, OLTP vs. OLAP, SQL vs. NoSQL, then a conceptual tour of graph databases—property graphs, hypergraphs, and RDF—positioned as the connective tissue for disparate sources. - **Middle (~45%–60%)**: The book's differentiating chapter on standardized vocabularies, terminologies, and ontologies (ICD, SNOMED-CT, OWL/RDF), covering how semantic technologies mitigate healthcare's harmonization problems. - **Late (~60%–85%)**: Moves into extraction and harmonization practice—pulling structured data from clinical text, weighing NLP tooling options, and building mappings and crosswalks across coding systems. - **Ending (~85%–100%)**: Applies the cleaned, harmonized data to feature engineering and ML/deep learning examples, with graph-based approaches for linking sources. (Excerpts do not cover the final chapters in detail.) 【Key Takeaways】 - **Collection context determines data quality** (Early): Healthcare data is generated for billing, compliance, and operations—not analysis—so understanding who enters codes and why is prerequisite to trusting any result. - **Harmonization is distinct from statistical normalization** (Early): Beyond scaling and centering, you must reconcile multiple representations of the same concept (brand names, generic names, internal hospital codes) into one canonical form. - **Diagnosis codes are billing artifacts, not clinical truth** (Early): The same encounter can carry screening, prediabetes, and internal dashboard codes simultaneously, so naive code-based cohorts will mislead. - **Database fundamentals still matter** (Middle): ACID, OLTP/OLAP, and SQL/NoSQL trade-offs are reviewed as vocabulary you'll need before evaluating graph alternatives. - **Graphs are a necessary but not sufficient tool** (Middle): Property graphs, hypergraphs, and RDF each model patient relationships differently; the author argues graphs are essential for connecting siloed healthcare sources at scale. - **Semantic vocabularies are the field's differentiator** (Middle): Terminologies and ontologies (ICD, SNOMED-CT, OWL/RDF) are what separate healthcare data work from generic data engineering. - **Clinical text requires deliberate extraction choices** (Late): Structured data hides in narrative notes, and tool/framework trade-offs for NLP and normalization should be made explicitly, not by default. - **Mappings and crosswalks bridge coding systems** (Late): Harmonization succeeds or fails on the quality of the crosswalks you build between terminologies. 【Reading Tips】 - Read Chapter 1 closely even if you're technical—the collection-incentive discussion prevents the most common analytical mistakes later. - Skim the database review (ACID, SQL/NoSQL) if you have a solid engineering background; slow down at the graph database section, which sets up later chapters. - Treat the vocabularies/terminologies chapter as the core—it's the author's stated differentiator and repays careful reading. - Keep the book's dual nature in mind: it alternates qualitative domain discussion with hands-on code, so match your pace to your background rather than reading linearly. - Take away the vocabulary and the "why was this collected?" habit; the specific tools will change, the framing won't. 【Coverage Limits】 This guide is based on stratified excerpts covering roughly the first half of the book plus the preface and foreword; the later hands-on ML, deep learning, and NLP chapters are only partially represented, so specific techniques and examples from those sections are not summarized here.
Page 5
to Healthcare Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 The Enterprise Mindset 2 The Complexity of...
View in text
Excerpt 2
domain knowledge and is not purely a function of only data. For example, we may need to find all of the ways the dataset might represent the idea of “Tylenol...
View in text
Excerpt 3
ntation, research paper, etc.), it would be that healthcare is inherently complex, the data is complex, and there is no silver bullet to address all of these...
View in text
Excerpt 4
resented as RDF to be self-describing. This is particularly important in the context of the semantic web because anyone should be able to pub‐ lish and link...
View in text
Excerpt 5
is maintained by the National Library of Medicine and made available as part of the UMLS but also accessible via a dedicated API. RxNorm contains both generi...
View in text
Excerpt 6
pts are defined, or how the various elements are connected. In Example 3-12, we have a Cypher query that starts with a search for atoms that con‐ tain the st...
View in text
Excerpt 7
, there are typical columns you would expect, such as time‐ stamps for starting or discontinuing the medication, or the ICU stay or hospital admission with w...
View in text
Excerpt 8
ns, while others attempt to handle some level of semantics. Some are quick to say that they are using graphs as the data model. While this may be true in a v...
View in text
Tags
AI categories
DataArtificial IntelligenceScience
ISBN: 109811292X
Publisher: O'Reilly Media
Publish Year: 2022
Language: English
Pages: 245
File Format: PDF
File Size: 5.8 MB
Text Preview (First 20 pages)
Registered users can read the full content for free

Register as a Gaohf Library member to read the complete e-book online for free and enjoy a better reading experience.

Generating text preview…