This deck was presented at the 4th Annual Medical Device Connectivity Conference (MDCC4) where Shahid Shah, CEO of Netspective Communications, described how creating a data-centric Backend-as-a-Service (BaaS) is good business and can generate new revenue for medical device vendors.
* Marketplace and industry challenges for device vendors
* Why connectivity is good business
* Why connectivity is a disruptive innovation
* What is a “Back-end as a Service” (BaaS)?
* There’s nothing special about health IT data that justifies complex, expensive, or special technology.
* Hardware, sensors, and software are transient businesses but data lives forever. He who owns, integrates, and uses data wins in the end.
* Data from devices is too important and specialized to be left to software vendors, managed service providers, and system integrators.
* Implement a data-centric hardware and BaaS technology strategy
Med Device Connectivity with a
BaaS is a Disruptive Innovation
Creating a data-centric Backend-as-a-Service (BaaS) is
good business and can generate new revenue
By Shahid N. Shah, CEO
Who is Shahid?
• 20+ years of embedded systems, software
engineering and multi-discipline complex IT
implementations (civilian government,
defense, health, finance, insurance)
• 12+ years specifically in healthcare IT and
medical devices experience
• Entrepreneur and founder of multiple
I blog at http://healthcareguy.com
Author of Chapter 13, “You’re
the CIO of your Own Office”
• Marketplace and industry challenges
for device vendors
• Why connectivity is good business
• Why connectivity is a disruptive
• What is a “Back-end as a Service”
• There’s nothing special about health
IT data that justifies complex,
expensive, or special technology.
• Hardware, sensors, and software are
transient businesses but data lives
forever. He who owns, integrates,
and uses data wins in the end.
• Data from devices is too important
and specialized to be left to
software vendors, managed service
providers, and system integrators.
• Implement a data-centric hardware
and BaaS technology strategy
What you’ll learn in this briefing
Data from devices is too important to be left to others
Why connectivity is good business
Looming 2.3% excise
tax provision of the
Affordable Care Act
timelines caused by
expectations due to
Lower margins as a
More complex and
longer sales cycles as
devices need IT
Raising money for
hardware is tougher
Customers trapped by
their EHR vendors are
begging for a way out
Device vendors aren’t
benefiting from industry
trends but can if they’re
smart about it
Customer base has
shifted from clinical to
clinical + IT + system
Clinical customer goals
have shifted from basic
automation to advanced
access to regulated IT
and system integration
skills is growing
You can use OSS to disrupt health IT
Healthcare industry / market trends
Major market and regulatory trends that are causing customers and competitors to shift
You must learn and be able to talk to customers about all these terms
Why care about MU?
If you’re not talking about MU you’ll find it harder to get in the door
2011 2013 2015
“Enable significant and measurable improvements in population
health through a transformed delivery system.”
MU Stage 1 MU Stage 2 MU Stage 3
Start planning for
Implications of healthcare trends
Evidence Based Medicine
Regulated IT and Systems
Don’t give up data to others without a fight
Software vendors, systems integrators, and others don’t have your best interest in mind
Data Transformation (ESB, HL7)
New revenue centers in software and services
Hardware Software Services
Build the right roadmap so that you don’t leave new revenue on the table
2 year ranking comparison of Top 30 HIT firms by offering type. Pure play firms are failing behind
Source - The 2012 Healthcare Informatics 100 ranks the leading 100 vendors by revenues derived from healthcare IT products and services earned in the U.S.
the way to go
% of all
How do you get started?
1. Use “integrated platform” to create “smarter” alarms by using
multiple data sources for earlier detection of events and more
meaningful alarms by improving alarm sensitivity and specificity.
(e.g. detect repeat small O2
desats that would not currently
trigger a conventional alarm). Crowd-source this activity.
2. Set “wider” alarm limits to decrease nuisance and false alarms
on each monitor/device. (e.g. SpO2
alarm at 80%). This
maintains “device level” alarms.
3. Collect clinical and alarm performance data to develop
algorithms and evaluate system performance. Document gaps
in current data sources and device capabilities.
4. Stop/adjust IV pump based on above.
Consider Dr. Julian Goldman’s proposal on improving the quality of clinical alarms
Data-centric device architecture
Extensibility and adaptability will be key in a data-centric world
Device Components 3rd Party Plugins
Security and Management Layer
(QNX, Linux, Windows)
Sensors Storage Display Plugins
Web Server, IM Client
Connectivity Layer (DDS, HTTP, XMPP)
• JDBC, Query
Ensure your devices fit in a modern IT architecture
Create a Back-end as a Service (BaaS) for your devices
Data Transformation (ESB, HL7)
E-mail [email protected]