Q to #mHealth developers: How attractive is new Epic API–allows you to add data to Epic EMR, but not take data? http://t.co/CWJRBrArhU
— Vince Kuraitis (@VinceKuraitis) September 18, 2013
Vince asks a good question. I wrote a little bit previously about the Epic User Group Meeting where they announced the Epic API. I definitely think there’s still a lot of missed opportunity for the announced Epic API, but hopefully what they’ve released is successful so it encourages them to open up their API much more.
Prediction: Market Saturation Will Slow EMR Growth: According to a market research firm, despite an upsu… http://t.co/5dEwCz0KiL #htm
— META (@METAbiomed) September 23, 2013
I’ve been writing a lot lately about the changing EMR marketplace (see Golen Age of EHR Over). This prediction offers a new insight I hadn’t covered. The market could decrease because many of the larger purchases are already done. So, that could slow the EHR spending.
#sidm2013 my faith in clinical decision support tools much increased by listening to Gordy's talk on how EMR-based prompts can improve dx
— YoryosLyratzopoulos (@GLyratzopoulos) September 22, 2013
I wish I could find this talk. I’m really interested in how properly implemented clinical decision support can save lives. That’s what this should be about anyway, no?
[…] it appears from this story that the API may be limited to only allowing one way writing of data to the Epic software without […]