Healthcare Directories
summary
FHIR directory mapping now uses Practitioner, PractitionerRole, HealthcareService, Organization, Location, Endpoint and the new VerificationResult and OrganizationAffiliation resources to represent real-world links and capabilities; NPPES exposes ~6 million provider rows with ~1.5M solo‑proprietor duplicates and many stale entries from 2007; geospatial boundaries use Base64 GeoJSON for coverage areas with near and contains search operators; synchronization options include polling, list membership, history export and subscriptions; the Validated Healthcare Implementation Guide (ONC-aligned) and Bulk Data $export support practical builds.
AI-written summary · about
chapters (22)
- 0:00Introduction to healthcare directories
- 3:18Types and roles of directories
- 6:25Provider vs services directories
- 7:50Key features of successful directories
- 9:16Data quality challenges in directories
- 10:24Organizational directory problems
- 13:18FIRE directory resources overview
- 14:02Evolution of FIRE directory standards
- 16:12Practitioner roles and locations
- 18:20Identifiers and security in FIRE
- 19:33Organization and location hierarchies
- 21:19Organization affiliations explained
- 22:01Practitioner vs practitioner role
- 23:04Endpoint resources and verification
- 24:29Searching in directories
- 25:54Geospatial and boundary searches
- 27:43Geospatial search enhancements
- 29:52Near and contains search methods
- 31:16Synchronizing directory data
- 33:05Bulk data and export options
- 33:50Validated healthcare implementation guide
- 35:16Summary and key takeaways
related talks
23mImplementing Provider Directory APIs
43mEnglish introduction to FHIR
45mIntroduction to FHIR
19mTurning data into better healthcare: data for hemophilia
34mIntroduction to FHIR for HL7 v2 experts
15mDeveloping Patient Access APIs at scale
47mLet's Build a FHIR Spec: Profiling with Forge
54mPlenary Session