Healthcare.MN presentation on health app development

Presentation on health app infrastructure, regulation, and data - with a focus on HIPAA and CCDA.

Transcript

1. Travis Good, MD, MBA | travis@catalyze.io | @travisjgpood building blocks for real world health and wellness apps data, infrastructure, regulations, and distribution
2. healthcare is broken Travis Good - 2013
3. Travis Good - 2013 the real world is shifting 1 reduce cost 2 better access 3 improve patient experience 4 increase provider happiness
4. Travis Good - 2013 real world needs - extend provider reach - redefine the patient - integrate data - engagement
5. technology is revolutionizing healthcare $12 $24 $36 $48 $60 2013 2018 (in billions) mHealth app market HIT market Travis Good - 2013 * 250 million app downloads last year * this is a really narrow view
6. Travis Good - 2013
7. in the next 5 years we’re going to see an explosion we’re already seeing it with social apps and business apps Travis Good - 2013 I think it’ll be bigger
8. amazing people and ideas are flooding in Travis Good - 2013
9. but building health apps is hard....and risky compliance data Travis Good - 2013
10. Travis Good - 2013 what regulation? 1 HIPAA 2 FDA 3 myriad of privacy groups
11. Travis Good - 2013 what is HIPAA - security, privacy, and breach rules - covered entities and business associates - PHI - protected health information - combine an identifier with an app, provider, or healthcare service - who is going to use the information
12. Travis Good - 2013 do as we demand, not as we do
13. Travis Good - 2013 basics of HIPAA - 1 encrypt - 2 do not share - 3 good auditing - 4 backups - 5 access controls - 6 breach notification (larger policy definitions)
14. Travis Good - 2013 Q - what makes HIPAA hard? A - 1 the cloud, 2 modern development practices, and 3 interpretability
15. Travis Good - 2013 1 the cloud 2 modern development practices 3 interpretability
16. Travis Good - 2013 * genetics redefining the patient - traditional definition - unstructured medical notes + payer data - episodic, clinical, snapshots - a better definition - continuous data - sensors + apps - little and big data - immediate feedback loops -> meaningful change
17. Travis Good - 2013 traditional data - EMR data - the old way - HL7 (Epic - “We support standards”) - some are attempting modern interfaces - a new way - CCDA (blacktm and jmandel on GitHub) - trust, push and pull - payer data - X12 standard - very messy - Eligible is a great use case for healthcare infrastructure
18. Travis Good - 2013 continuous data - quantified self is huge - today - motivated healthy (10-12%) - tomorrow - unmotivated unhealthy (the rest) - building a new world of silos - lots of different RESTful services - unifiers are emerging - CarePass, HumanAPI, Validic, Singly, catalyze.io
19. integrate it all and make it meaningful - EMRs are the default (they currently own the providers) - EMRs were not built to do this - EMRs are slow movers Travis Good - 2013
20. building something? 1 be thoughtful about HIPAA 2 look at CCDA and Eligible 3 focus on distribution 4 signup for catalyze.io Travis Good - 2013
21. thanks! Travis Good - 2013 Travis Good travis@catalyze.io @travisjgood
22. appendix Travis Good - 2013
23. catalyze.io solves two pain points for developers compliance data Travis Good - 2013
24. add secure and scalable backend services in minutes build and test full-featured, interoperable apps for free Travis Good - 2013
25. the catalyze.io difference current way catalyze way 1. read & interpret HIPAA rules 2. configure and maintain cloud servers to meet HIPAA rules 3. identify data sources 4. develop data models 5. map data sources 1:1 6. build and test your own API 7. start building app 1. get API key and SDK 2. start building app cut development time and cost by 60-70% Travis Good - 2013
26. catalyze.io API SDKs HL7 CCDA RxNorm LOINC EDI APIs x n hospital pharmacy lab payer quantified self User authentication Data storage Unified person Secure messaging Travis Good - 2013