Atostek Oy. How modern suppliers. add value in healthcare systems? Mika Torhola

Transcription

1 How modern suppliers add value in healthcare systems? Mika Torhola

2 Founded employees Turnover 3,5 M (2014) Location: Tampere 2

3 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 Nudity! Perspective! 3

4 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 Do the texts in bold add value? 4

5 Closed Systems vs Data Interchange? Old school Nothing new here, either Hype CDA R2 (Clinical Document Architecture) XDS (Cross Enterprise Document Sharing) 5

6

7 Proprietary vs Open Source? Some aspects of added value: Security Quality Customizab ility Freedom Flexibility Interopera bility Auditability Support options Cost Try before you buy 7

8 Some Existing Open Source Health Care SW Libraries and toolkits Back-end implementations (eg. XDS or DICOMarchive) EMR/EHR implementations Integration Platform (IPF) DCM4CHEE (PACS) 8

9 Producing Healthcare SW as Open Source? Completely another story. 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 9

10 Producing Healthcare SW as Open Source? 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! 10

11 Producing Healthcare SW as Open Source? Existing work in public sector: We need more pilot projects! Tuotteenhallintasuunnitelman tekoa pilotoitu Pilviväylä -hankkeessa 11

12 Functionality 1 Functionality 2 Functionality 3 Functionality 4 Functionality 5 Functionality 6 Functionality 7 Functionality 8 Functionality 9 Atostek Oy Monolithic vs. Modular? What does that even mean? Monolithic system A Monolithic system B Monolithic system C Monolithic system D 12

13 Functionality 1 Functionality 2 Functionality 3 Functionality 4 Functionality 5 Functionality 6 Functionality 7 Functionality 8 Functionality 9 Atostek Oy Monolithic vs. Modular? What does that even mean? Modular system A Modular system B Modular system C Modular system D 13

14 Local vs. shared installations? 14

15 Local vs. shared installations? Shared installation needs elaborate internal modeling of organisations, departments, users, etc. 15

16 What should we call an integratable functional module with UI, that needs only one shared installation? 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 16

17 Business model? Proprietary business model Standard Open source business model Hybrid business model Sell licenses and maintenance for closed product Sell support and maintenance subscriptions for OS product Run and sell a SaaS service, which is based on OS platform, but has proprietary added value components. Contribute strongly back to OS. 17

18 So, archetype of a modern healthcare IT system / provider, [that adds value]? XDS.b Hybrid business model 18

19 Atostek s endeavor: era eprescription SaaS microservice KanTa-EHR SaaS microservice Not a full archetype of modernity, but satisfies some aspects of it 19

20 Thank You! Mika Torhola