Implementing Provider Directory APIs

on YouTube ↗23m

" summary

Reference implementation converts public CMS/NPPES CSVs into a validated FHIR store: files land in Google Cloud Storage, run through Dataflow (Apache Beam) jobs to NDJSON, then transform via VESSEL mappings into FHIR transaction bundles and write 74 validated resource types into Firestore with Firestore validation against DaVinci PDEX PlanNet / US Drug Formulary profiles. It includes reconciliation/deduplication rules, partner NPI enrichment, and app registration + OAuth via Health API X portal.

AI-written summary · about

" chapters (9)

1. 0:00Introduction
2. 0:15Overview
3. 3:10Reference Implementation
4. 8:30Conversion
5. 14:15Questions
6. 14:47Format of CSV files
7. 16:10Source data
8. 17:05Different patients
9. 17:55Resolving duplicate providers

" related talks

• 36mHealthcare DirectoriesBrian Postlethwaite · HL7 FHIR DevDays 2019 Redmond
• 20mPrototyping data ingestion pipelinesBrady Fausett, Emma Stephenson · DevDays 2023
• 46mThe FHIR Bulk Data API and what's new in v2!Dan Gottlieb · DevDays 2023
• 37mA novel way to manage and represent unstructured clinical dataRuchika Kharwar · HL7 FHIR DevDays International 2022
• 46mC-CDA on FHIRRick Geimer · HL7 FHIR DevDays Boston 2018
• 18mRelevant technologies for CMS-0057-P and CMS-0053-PRich Almeida · DevDays 2023
• 16mThe story of FHIR data exchange and storage combinedMarcel Hofman · DevDays 2023
• 43mLet's Build! Patient Mediated Data ConnectivityRicky Sahu · HL7 FHIR DevDays 2019 Redmond