mika torhola
TRANSCRIPT
Atostek Oy
How modern suppliers add value in healthcare systems?
22.9.2015
Mika Torhola
Atostek Oy
2Atostek Aatos - Tueksi hankintoihin30.9.2015
• Founded 1999
• 43 employees
• Turnover 3,5 M€ (2014)
• Location: Tampere
Atostek Oy
Definition of modern?Is modern by default something to strive for?
• “involving recent techniques, methods, or ideas”
• “of or relating to present and recent time; not ancient or remote”
• “characteristic of present and recent time; contemporary; not antiquated or obsolete”
• “of or relating to the historical period following the Middle Ages”
• “new”
3Atostek Aatos - Tueksi hankintoihin30.9.2015
Nudity! Perspective!
Atostek Oy
Characteristics of modernity [in health IT]?
• Closed system vs. data interchange
• Proprietary vs. open source
– Subcategory A: Using Open Source components
– Subcategory B: Producing Open Source SW
• Monolithic vs. modular
• Local installations vs. shared installation
• Business model: Proprietary licensing vs. “pure open source” vs. “hybrid”
4Atostek Aatos - Tueksi hankintoihin30.9.2015
Do the texts in bold add value?
Atostek Oy
Closed Systems vs Data Interchange?
5Atostek Aatos - Tueksi hankintoihin30.9.2015
Old schoolNothing
new here, either
XDS (Cross Enterprise Document Sharing)
CDA R2 (Clinical Document Architecture)
Hype
Atostek Oy
Atostek Oy
Proprietary vs Open Source?Some aspects of added value:
7Atostek Aatos - Tueksi hankintoihin30.9.2015
Security
Try before you buy
Freedom
Auditability Support options
Quality
Flexibility
Cost
Interoperability
Customizability
Atostek Oy
Some Existing Open Source Health Care SW
8Atostek Aatos - Tueksi hankintoihin30.9.2015
Libraries and
toolkits
Back-end implemen-tations (eg.
XDS or DICOM-archive)
Integration Platform (IPF)
EMR/EHR implemen-
tations
DCM4CHEE(PACS)
Atostek Oy
Producing Healthcare SW as Open Source?Completely another story.
9Atostek Aatos - Tueksi hankintoihin30.9.2015
Let’s assume a context: Health Care Software for Finnish public sector
Simple process?
Develop 1.0 for organization A
Deploy 1.0, agree on running as
service
Develop 2.0 for organization B
Atostek Oy
Producing Healthcare SW as Open Source?
10Atostek Aatos - Tueksi hankintoihin30.9.2015
Just a few real world questions that need to be tackled:
1. Development decision-making (governance)• Who decides, what features are allowed / will be implemented to 2.0?
• Ie., who is the ”owner” of the SW• What is the decision making process?
2. Funding• Development of features?• Running SW as service for later organisations? • Procurement legislation: Yikes!
Atostek Oy
Producing Healthcare SW as Open Source?
11Atostek Aatos - Tueksi hankintoihin30.9.2015
Existing work in public sector:
13.9.2011
Tuotteenhallintasuunnitelman tekoa pilotoitu ”Pilviväylä”-hankkeessa
We need more pilot projects!
Atostek Oy
Fun
ctio
nal
ity
2
Fun
ctio
nal
ity
3
Fun
ctio
nal
ity
4
Fun
ctio
nal
ity
5
Fun
ctio
nal
ity
6
Fun
ctio
nal
ity
7
Fun
ctio
nal
ity
8
Fun
ctio
nal
ity
9
Fun
ctio
nal
ity
1
Monolithic system C
Monolithic vs. Modular?What does that even mean?
12Atostek Aatos - Tueksi hankintoihin30.9.2015
Monolithic system A
Monolithic system B
Monolithic system D
Atostek Oy
Fun
ctio
nal
ity
2
Fun
ctio
nal
ity
3
Fun
ctio
nal
ity
4
Fun
ctio
nal
ity
5
Fun
ctio
nal
ity
1
Fun
ctio
nal
ity
6
Fun
ctio
nal
ity
7
Fun
ctio
nal
ity
8
Fun
ctio
nal
ity
9
Modular system C
Monolithic vs. Modular?What does that even mean?
13Atostek Aatos - Tueksi hankintoihin30.9.2015
Modular system A
Modular system B
Modular system D
Atostek Oy
Local vs. shared installations?
14Atostek Aatos - Tueksi hankintoihin30.9.2015
Atostek Oy
Local vs. shared installations?
15Atostek Aatos - Tueksi hankintoihin30.9.2015
Shared installation needs elaborate internal modeling of organisations, departments, users, etc.
Atostek Oy
What should we call an integratable functional module with UI, that needs only one shared installation?
16Atostek Aatos - Tueksi hankintoihin30.9.2015
How about eHealth microservice?
”You need to have a single source of truth, but not necessarily in one place.”
“In short, the microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies.”
-- Martin Fowler
Atostek Oy
Business model?
17Atostek Aatos - Tueksi hankintoihin30.9.2015
Proprietary business model
”Standard” Open source
business model
Hybrid business model
Sell support and maintenance subscriptions for OS product
Sell licenses and maintenance for closed product
Run and sell a SaaS service, which is based on OS platform, but has proprietary added value components. Contribute strongly back to OS.
Atostek Oy
So, archetype of a modern healthcare IT system / provider, [that adds value]?
18Atostek Aatos - Tueksi hankintoihin30.9.2015
XDS.b
Hybrid businessmodel
Atostek Oy
Atostek’s endeavor:
19Atostek Aatos - Tueksi hankintoihin30.9.2015
eRA• ePrescription SaaS microservice• KanTa-EHR SaaS microservice• Not a full archetype of modernity, but satisfies some aspects of it