APIdays Helsinki 2019 - Build the API and they will come? Experiences from the Finnish Kanta PHR Ecosystem with Mikael Rinnetmäki, Sensotrend
•Download as PPTX, PDF•
1 like•127 views
Build the API and they will come? Experiences from the Finnish Kanta PHR Ecosystem, Mikael Rinnetmäki, Founder of Sensotrend
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to APIdays Helsinki 2019 - Build the API and they will come? Experiences from the Finnish Kanta PHR Ecosystem with Mikael Rinnetmäki, Sensotrend
Similar to APIdays Helsinki 2019 - Build the API and they will come? Experiences from the Finnish Kanta PHR Ecosystem with Mikael Rinnetmäki, Sensotrend (20)
More from apidays
More from apidays (20)
Recently uploaded
Recently uploaded (20)
APIdays Helsinki 2019 - Build the API and they will come? Experiences from the Finnish Kanta PHR Ecosystem with Mikael Rinnetmäki, Sensotrend
- 1. …making sense of diabetes trends
- 3. @sensotrend
- 4. @sensotrend
- 6. Build the API and they will come? Experiences from the Finnish Kanta PHR Ecosystem
- 9. Documentation � Well documented � Linked PDF docs? 👍
- 11. HL7 FHIR Health Level Seven – Fast Healthcare Interoperability Resources
- 13. 👍 Based on standards � REST / JSON, GraphQL, … � Very hot specification � Proprietary codings � Strict profiles � Absolute minimum implementation
- 16. 👍 Sandbox environment � Essential to have � Self service scales well � Multiple levels: no-auth, auth, acceptance test � No paid registration, no bureaucratic process � Matches reference implementations � Occasional cryptic error messages � Profile creation requires expertise
- 17. Community
- 21. 👍 Community � Exists � Connection to international forums � Multiple modes of communication � Clock speed is low, although increasing � Size of the community is still small in Finland
- 22. Decision making
- 24. 👍 Decision making � Everyone can participate � Open, well-defined process for gathering comments and requirements � Everyone is not part of the decision making process � Some things just get stuck on upper levels…
- 25. Incentives
- 27. 👎 Incentives � Kanta brand � Trust in government � Integration with healthcare organizations � Well defined business models
- 28. Final verdict
- 30. Mikael Rinnetmäki mikael@sensotrend.com +358 50 3855511 @mrinnetmaki …making sense of diabetes trends
Editor's Notes
- Minä olen Mikael, Sensotrend-startupista. Me kehitämme automaattista diabetespäiväkirjaa.
- Tyypin 1 diabeteksen hoito edellyttää jatkuvaa mittaamista ja mittaustuloksista oppimista.
- Mittaaminen on nykyään helppoa. On sensorit, on sovellukset. Kaikesta mitatusta datasta oppiminen on kuitenkin edelleen haastavaa.
- Tässä Sensotrend auttaa. Me yhdistämme tiedot yli 60 hyvinvointisovelluksesta ja 30 lääkinnällisestä laitteesta, visualisoimme sen diabeteksen hoidon kannalta olennaisella tavalla ja autamme jakamaan sitä lääkärin, hoitajan ja vertaistuen kanssa.
- Based on my own categorization of what makes an API good! We integrate with a bunch of devices and services. We have some experience. Hope that some of the insights are applicable in other domains too. If you’re considering building an API. Hope some of you will be encouraged to check this API out in more detail.
- What is this about? How does it work?
- Based on standards Essential, don’t invent your own stuff! Strip away all the essential features? Start with absolute minimum, then keep adding features per request. Invent proprietary codings, rather than using existing ones or proposing new ones to be standardized
- Do we need to learn something from scratch? Is what we learn applicable anywhere else?
- Yes. REST/JSON, GraphQL, … Domain specific very hot specification Strip away all the essential features? Start with absolute minimum, then keep adding features per request. Invent proprietary codings, rather than using existing ones or proposing new ones to be standardized
- Photo by Matt Howard on Unsplash App stores of EHR system vendors are just being opened. They currently have from 20 to 120 apps available. Now is the time!! http://allscriptsstore.cloud.prod.iapps.com/search-by-all-apps https://code.cerner.com/apps https://apporchard.epic.com/Gallery https://apps.smarthealthit.org/
- Based on standards Essential, don’t invent your own stuff! Strip away all the essential features? Start with absolute minimum, then keep adding features per request. Invent proprietary codings, rather than using existing ones or proposing new ones to be standardized
- Based on standards Essential, don’t invent your own stuff! Strip away all the essential features? Start with absolute minimum, then keep adding features per request. Invent proprietary codings, rather than using existing ones or proposing new ones to be standardized
- When you run in to issues, want to get connfirmation or give feedback…
- Based on standards Essential, don’t invent your own stuff! Strip away all the essential features? Start with absolute minimum, then keep adding features per request. Invent proprietary codings, rather than using existing ones or proposing new ones to be standardized
- Compared with Google, Apple, Moves, Dropbox, … Epic, Cerner, … Some things just get stuck on upper levels of decision making… Authentication Lab results
- What’s in it for me? Does this API address the real issues for foreseen users of the API?
- Photo by Christine Roy on Unsplash Various currency bills pinned to a large world map with colorful pins in various locations Kuinka tästä tehdään liiketoimintaa / kuinka saadaan liiketoiminta tukemaan tätä (ja toisin päin). Kuinka tällä tehdään rahaa?
- Integration with providers is a need, does this API help? Seems to do the opposite. Professionals use separate apps. Wellness instructors / coaches cannot use the data at all? Whom can I send an invoice to? Based on what? The ministry is not concerned of well-being of companies.
- It’s just the international aspect of this all that perhaps makes it worthwhile for us to be involved. We also like the basic idea of PHRs.