This document discusses telehealth at UCSF and its three main components: live video, store-and-forward technologies, and remote patient monitoring. It describes telehealth's organizational structure and how it allows UCSF to expand its referral network and expertise. The document also discusses a model called the "Daschle Cone" that shows how telehealth can deliver different levels of care both vertically through different specialties and horizontally across locations. It notes some challenges of adopting telehealth including technology, integration, and getting clinicians onboard.
2. Three legs of Telehealth
• Live-Video
– Cisco gives us a very strong position
• Store & Forward
– Asynchronous consultations such as
eConsult/eReferral, Tele-Derm and
Tele-Ophthamology
– PACs and EHR integration
• Remote Patient Monitoring
– Enabling the Ubiquitous vs. Episodic care paradigm
3. Telehealth’s Organizational Position
• Governance
– The Telehealth Resource Center reports to the
Telehealth Steering Committee
• Strategic tool that allows UCSF to:
– Build an extended referral network
– Export UCSF’s expertise and brand via remote
consultation and education
• Tactical tool that allows UCSF to:
– Collaborate intra-campus/intra-specialty
– Create dispersed yet integrated teams
– Expand our research coverage
4. Senator Tom Daschle visits UCSF
• Senator Daschle: “Health care in any society looks
like a pyramid. The base of the pyramid comprises
basic health care delivery involving wellness and
prevention. It is the least costly. As we move up
the pyramid, the care becomes more sophisticated
and technologically advanced. At the peak are the
most costly and technologically advanced
applications, such as organ transplants, available
in modern medicine today.”
• “Every country begins at the base of the pyramid
and works its way up until the money runs out.
However, in the U.S., we start at the top of the
pyramid and work our way down until the money
runs out. This is our fundamental problem.”
Oct 3rd 2012
5. UCSF Telehealth develops
The Daschle Cone
• Tom Daschle is right however he offers no specific
solution
• So we developed The Daschle Cone to explain how
distributed interactions would look both vertically
and horizontally
Jeffrey Olgin, Chief of
Cardiology, leads a
large-scale digital
version of the
Framingham Heart
Study – Health eHeart
UCSF
Local Clinic
Live
Homecare
Remote Patient
Monitoring
Wellness
Telehealth
mHealth
6. A patient’s journey through
the Daschle Cone
UCSF
Local Clinics
Live Homecare
Remote Patient
Monitoring
Wellness
Pro-Active
In Patient Specialized
Care and Education
Tracking
conditions
Triage
Tracking issues
Follow up New NormalConsult
14. How Automated Telephony Self-
Management works
TheVoicePlatform
UCSFsystems
Outbound
SMS
Inbound
SMS
Outbound
Voice
Web
Version
Inbound
Voice
BasicScripting Rules
Text toSpeech
Engine
RecordedVoice
Files
Timer
(Trigger)
Salesforce
Client
the
WWWTelephone System
18. Telehealth Focus Areas
• Mission Bay
– Intra-campus consultations (MB, M/L, Mt Z.)
– Intra-campus & inter-facility case conferences
• Telehealth Outreach
– Inter-facility consultations
• Kaiser: Heart & Lung Transplant
• Pediatrics: CHO, CHCC Madera, Washington,
Mad River, Marin General
• Neurology: Contra Costa
• ED: San Joaquin General
19. Beware the hype
• “Physicians at UC Davis began practicing
telemedicine in 1992”
(http://www.ucdmc.ucdavis.edu/ucdavishealth/issues/spring2014/tele
medicine-leading-a-revolution.html)
• So why hasn’t UCD blanketed California?
• Factors:
– Technology
– Integration
– Adoption
20. Adoption
• Dis-rup-tive:
– innovative or groundbreaking;
– troublesome, undisciplined, unmanageable,
uncontrollable, obstreperous;
• Normalisation Process Theory (Carl R. May PhD)
– Four factors of success:
• Local and/or National Policy sponsor
• Structural/Technical integration
• Enrollment of cohesive, cooperative groups
• Integration at the level of professional knowledge and
practice, where clinicians are able to accommodate
technology through the development of new
procedures and protocols
Editor's Notes
Store and forward we have a good idea of what needs to happen
For RPM we need to understand the balance between cost and value
Most of the arrows are web service style of calls. The Salesforce.com client would be able to store information and set a trigger for something to happen at an appropriate time. So the gate keeper for Salesforce.com is the client and a limited set of data that relates to what is pushed out to Voxeo. Also the status for the messages would come back to Salesforce.com when it is defined. So If Salesforce.com requests a message to be sent to a phone, where this is done at 2am, and the persons contact window opens at 7 am, Salesforce.com could see that the message was queued until 7am when the person wants to receive messages. Then when it is delivered, that status would comeback into Salesforce.com . Think of the rule, it could most likely be implemented. The take away from this is: there is a nice set of phone capabilities that becomes possible, and can be implemented into UCSF to increase communication by being able to push information to a phone.