Download to read offline
Uploaded byVaibhav Bhandari
The Cathedral And Data Bazaar - Enabling Lean Data!
The document discusses enabling "lean data" by moving away from a centralized, monolithic model of healthcare data towards a decentralized "bazaar" model. It proposes a simple platform where data is judged and consumed based on its value. The pillars of such a model are described as transport using standards like FTP and FHIR, common data formats like CSV and FHIR, and agreed upon semantics like SNOMED-CT and LOINC. Security is achieved through standards like SSL and OAuth while still prioritizing simplicity. Sharing focuses on immediate value through measures and eventually more advanced standards like XACML. The model is presented as an alternative to current approaches that aims to free data through valid "crawl, walk, run" approaches.
More Related Content
Similar to The Cathedral And Data Bazaar - Enabling Lean Data!
The Cathedral And Data Bazaar - Enabling Lean Data!
- 1. The Cathedral AndThe Data Bazaar Enabling Lean Data @vaibhavb
- 2. Who is Vaibhav? DIRECTOROF PRODUCT MANAGEMENT, OPTUM AUTHOR, O’REILLY MEDIA TWITTER – @vaibhavb BLOG – http://healthblog.vitraag.com ME – http://about.me/vaibhavb Hobbies: Interactive Furniture, Mixology, Cycling, Mountaineering Associations: United States Cycling Federation (USCF) Referee
- 3. Agenda • The Cathedralmodel for Healthcare Data • The Bazaar - Lean Data • Clinical Data Connectivity – Purpose – Access – Security – Sharing
- 5. Problem with currentmodel(s) • Central Monolithic design with too many interdependencies • Hard to see value when doing data aggregation • At scale & adoption issues for data sets released – Open Data – Meaningful Use Mandated data • Design by committee
- 6. ONC “Learning HealthSystem” Roadmap • 10 years! • Over 50 use cases • A standards advisory issued every year
- 7.
- 9. Bazaar – LeanData • A bare bones simple platform • Participants can create and absorb value independently • Data is judged and consumed by value!
- 10. Lean Data –A Case Study Value Based Consumers Paper Charts EMRs Labs Clinical Data Aggregation
- 11. Purpose First! • DriveMeasures – ABA: Adult BMI Assessment – CDC-LDL: Comprehensive Diabetes Care & LDL screening – ..
- 12. Pillars of Access •Transport • Format • Semantics
- 13. Data Transport • SecureFTP • XDS.B • Direct • Proprietary REST API • FHIR REST API
- 14. Format • Proprietary CSVFiles • HL7 V2 (ADT, ORU etc.) • C32 • CCDA • FHIR JSON
- 15. Semantics • Problems – ICD9/ 10 – SNOMED-CT • Procedures – CPT • Labs – LOINC • For example BMI values require SNOMED-CT codes
- 16. Security • Self SignedX509 Certificates – SFTP – SSL Mutual Authentication (XDS.B/ REST API) • Direct Certificates & Identity Proofing – Direct • O-Auth2 – FHIR 16
- 17. Sharing – DataAccess • Data Access – Simple • Member Demographics (First Name, Last Name etc.) shared with Data Provider • Data Shared only on a full match! – Standards Based • IHE PIX/PDQ 17
- 18. Sharing – DataUse • Data Use established per use-case / measure • Eventual standards based – XACML • Data shared with HEDIS engines through network share in flat files – Lean! 18
- 19. Data Value ==Data Freedom • When you are freeing the data make sure there is immediate value! • Choose Lean vs. end all be all • Establish valid crawl, walk run approaches for – Access – Security – Sharing
- 20. Thank You! Questions? TWITTER –@vaibhavb BLOG – http://healthblog.vitraag.com ME – http://about.me/vaibhavb