M health@ucsf


Published on

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • I came from Apple – really one of the golden eras of Silicon Valley iPod to iPad. Emphasis on integrated systems, user centric design. A certain smoothness and fluidity to the approach to problems and goals. I joined UCSF in January as the Assistant Director of TeleMedicine. It turns out the American TeleMedicine Association considers mHealth part of TeleMedicine. What’s mHealth? mHealth stands for mobile Health. You’ll see various definition. What I’d like to think is when people look at UCSF they’ll say. Now that’s mHealth. But I am getting ahead of myself.
  • This is what I found at UCSF. I started meeting you. I or my team have probably sat down with half of you here. I learned about the Grant process. Things became clearer.
  • It costs a lot to develop mobile apps. Some had good relationships with their vendors, I’d say the majority though had items that could be improved. Grants often want examples of a technology that does not yet exist and in fact part of the grant is expected to pay for. Who else was working on mobile apps? Patient Centric. Looking at ways to reach out to your patients. We started a brown bag series. Collaboration - Pain map example. We may have ended up paying for this multiple times – we still might. But it’s a lot less likely now.
  • So we (mostly Larry Suarez) took the approach of defining a mobile architecture which could use layers to abstract the functions needed to run an application on a mobile device and using XML as the input to create the application itself. Basically an application generator. This is what I call a takeaway slide. Its my favorite slide because as an engineer I like these sorts of diagrams however its too busy for today.
  • We noted these common functions. The framework was designed to allow us to drastically reduce the time to be able to provide a prototype. Overcoming the grant catch-22. Allows for an iterative process because we make quick changes so we can measure hands-on effectiveness. We can track it. Allows us to be flexible. We need to be able to move quickly because the technology will move quickly. So we can become very agile front-end for the point of care.
  • So if you think of the point of care as the front-end we have half the equation and I think the most fun part. Here’s where the hard work comes in. The back-end or what some facetiously call “the plumbing”. Mobility will allows to gather copious amounts of data. We already have copious amounts of data. How do we access and utilize information as seamlessly as possible? And remember - Mobile is just a part of this. This sort of framework lets us deliver the right information precisely where it is needed, when it is needed. It’s a big job, but the good news it can be done in steps and UCSF is not alone.
  • This is how we can shorten the times to deliver the hard work. We seek out partners to collaborate with. Leverage their expertise to help us create an integrated mobile technology framework. With the Operational Excellence and Epic initiatives underway this is a great opportunity to create a platform for UCSFs mHealth visions to be realized
  • And what is that vision? I think finding the answer to that question is why we’re all here. I just wanted to share with you Intel’s vision, shot at TedMed in November of 2009. A year ago.
  • Why did I choose these companies? The promise of mhealth is the ability to connect as many people as possible with not just healthcare but wellness. It really needs to be solved in two directions. Enterprise models that scale and “hands-on” patient interactions. What is UCSFs vision?
  • What we need to create
  • M health@ucsf

    1. 1. Managing  the  mHealth technology framework
    2. 2. Current State: Silo <ul><li>Engaging niche vendors such as GoMed, Dynamic Clinical Systems, Medsleuth… </li></ul><ul><li>Partnering with Institutions and Organizations – ISIS, SANA, UCLA, Stanford… </li></ul><ul><li>Internal Depts: </li></ul><ul><ul><li>UCSF Library – Internal web app development </li></ul></ul><ul><ul><li>Radiology – 3-4 person team developing iPad apps </li></ul></ul><ul><ul><li>Information Services Unit, Telemedicine Program, Mobile Development Group – architect, project manager, developers and designers </li></ul></ul>
    3. 3. What you told us <ul><ul><li>Too expensive </li></ul></ul><ul><ul><li>Frustration with the process </li></ul></ul><ul><ul><li>Grant – Catch 22 </li></ul></ul><ul><ul><li>Technical assistance </li></ul></ul><ul><ul><li>Access to data/systems </li></ul></ul><ul><ul><li>Common interests </li></ul></ul>
    4. 4. Our approach <ul><li>Cross platform </li></ul><ul><ul><li>Write once, run everywhere </li></ul></ul><ul><li>Supports clinical pathways </li></ul><ul><li>Secure local data storage available </li></ul><ul><li>Scheduled interactions (Daily, weekly, quarterly, etc.) </li></ul><ul><li>Surveys </li></ul><ul><li>Multimedia (display videos, play audio, show HTML pages, text files) </li></ul><ul><li>Symptom tracking (eg. Episodes of nausea, pain) </li></ul><ul><li>Event logging (eg. Ate a meal, smoked a cigarette) </li></ul><ul><li>Capture, store and transmit photographs </li></ul><ul><li>Graphing </li></ul>
    5. 5. What it means <ul><li>Quickly provide prototypes for: </li></ul><ul><ul><li>Surveys </li></ul></ul><ul><ul><li>Scheduled interactions/reminders </li></ul></ul><ul><ul><li>Event Logging </li></ul></ul><ul><ul><li>Symptom Tracking </li></ul></ul><ul><ul><li>Clinical Pathways </li></ul></ul><ul><li>Multi-media: play videos, audio </li></ul><ul><li>Multiple Platforms (iPhone, iPad, Android, Flip-Phones) </li></ul>
    6. 6. Enterprise Application Integration Middleware/Engine/Framework patient IDR Analytics education research UCare Etc… EPIC SSIS
    7. 7. Integrations/Partners <ul><li>EPIC </li></ul><ul><li>Blackboard </li></ul><ul><li>Inkling </li></ul><ul><li>VitalHub </li></ul><ul><li>Mashery </li></ul><ul><li>Sales Force </li></ul><ul><li>Apple </li></ul><ul><li>Sybase Mobile Device Management </li></ul>
    8. 8. Mainframe vs Personalized Healthcare
    9. 9. Other visions <ul><li>Microsoft’s vision: </li></ul><ul><ul><li>http://www.youtube.com/watch?v=V35Kv6-ZNGA </li></ul></ul><ul><li>Cisco’s vision: </li></ul><ul><ul><li>http://www.youtube.com/watch?v=XYhUM8ukA5I </li></ul></ul><ul><li>Qualcomm vision: </li></ul><ul><ul><li>http://www.youtube.com/watch?v=vB6S77oGMjs&feature=related </li></ul></ul><ul><li>UCSF’s Vision? </li></ul>
    10. 10. Contact info Jeff R Jorgenson 415-476-5202 [email_address] https://wiki.library.ucsf.edu/display/MobileApps/Home
    11. 11. Appendix
    12. 13. Server Side <ul><li>Once the data is sent to the server, the possibilities open up! </li></ul><ul><li>HIPPA compliant </li></ul><ul><li>Secured server database </li></ul><ul><ul><li>AES data encryption available </li></ul></ul><ul><li>Usage statistics and reports </li></ul><ul><li>Ad hoc and designed reporting </li></ul><ul><li>Notifications and escalation </li></ul><ul><ul><li>Know when a patient needs your help </li></ul></ul><ul><ul><li>Send email, schedule reports, phone calls in response to data the users enter </li></ul></ul><ul><ul><li>Send custom messages to all or selected users </li></ul></ul>