API’s in public healthcare – case Health Village
summary
Nationwide Health Village runs as a Microsoft Dynamics/Azure microservice platform with an integration hub that exposes data via FHIR and HL7 while coding clinical content with SNOMED; it records about 700,000 page views/month, hosts roughly 230 care paths (20–30 actively used), 1,500 professionals and ~25,000 registered patients. It connects EHRs, IoT and Apple Health/Fitbit feeds into a data lake, uses publish/subscribe for distribution, is building predictive models, and struggles with monolithic APIs, refactoring and strict public procurement/security rules.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:04HEALTH VILLAGE INMATIVE
- 4:21HEALTH VILLAGE PLATFORM
- 6:13HEALTH VILLAGE TECHNICAL ARCHITECTURE
- 11:12EXPERIENCES OF API DEVELOPMENT
- 15:20SIMPLIFIED INTEGRATION SOLUTION
- 16:44CHALLENGES
- 18:59ECOSYSTEM
- 21:16CONNECTIVITY ROADMAP 2019
related talks
20mMastering API Management for Enhanced Patient Care
33mHealthcare Interoperability : From Buzzword to APIs
26mUsing APIs to Transform the way CMS Shares Medicare Claims Data
13mLightning Talks - Leveraging APIs to Transform Healthcare
26mFireside Chat
30mBuilding high-performance API platform teams
28mTransforming Digital Services with API Integration
27mShop & cook & serve your public health data with NHSNLink