What it takes to process healthcare data?
summary
IQVIA processes 600 million de-identified patient records from roughly 1 million data feeds and 140,000 suppliers, so engineering focuses on scale, sliding cost, and constant ingestion rather than batch rebuilds. Systems implement privacy impact assessments to measure re-identification risk, support re-bulking and opt-out removal, map many local drug/diagnosis dictionaries into a global ontology, and choose stacks like Cloudera/Databricks for ingestion and Snowflake for BI. Operational choice favors format-specific plugins over forcing a single input standard.
AI-written summary · about
chapters (12)
- 0:00Processing healthcare data intro
- 2:29IQVIA healthcare data scope
- 5:01Big Data in healthcare
- 6:07Scaling healthcare data challenges
- 10:25Complexity of medical data
- 12:57Regulations and data privacy
- 16:24Privacy impact assessment
- 20:19Data supplier agreements
- 28:51Standardizing data formats
- 31:58Data dictionaries interoperability
- 36:33Healthcare data challenges summary
- 38:20Q&A
related talks
31mAI in healthcare: Data driven transformation
41mAccelerating privacy-enhancing data processing
33mHealthcare "big" Data from Data Management to Web Apps
07mData Collection and Reorganization
54mUntangling Healthcare with Spark and Dataflow
10mHealth Data Anonymization and Privacy
17mHealth Care Analytics: The Key Is Integration
28mHerding Data to the Cloud
