We’re back with our weekend round up of interesting tweets from the Twittersphere. We’ve got some really interesting ones to consider this week. So, much is happening in healthcare IT. Hopefully I can provide a good insight to some of the trends that are most interesting. No doubt this will be a challenge as we head into what is one of the most busy healthcare IT news cycles of the year around HIMSS.
Now, on to the various EHR and Healthcare IT tweets:
— Jennifer Dennard (@SmyrnaGirl) January 30, 2012
Kaiser Permanente just made 9 Million EHR records available on line to the patients. That’s definitely worth talking about. Go read about it in Jennifer’s post.
This tweet just made me laugh (although, if you’re experiencing it, it’s not that funny):
— Alicia C. Staley (@stales) January 30, 2012
I think they probably need a DSM-IV code.
What if the patient was the repository of their own data – perhapsQcode on my phone to my EHR? plug into me not my data #hitsm
— Sherry Reynolds (@Cascadia) January 27, 2012
I know there are a number of companies working on this. The problem isn’t the technology to get the Qcode to access your patient record. It’s aggregating your patient record in some place so that it’s accessible. That’s going to take a long time (if ever) to get it all connected.
— Brian Ahier (@ahier) January 26, 2012
I’m fascinated by this idea as well. I hope some companies will take it really seriously. The interesting thing is that often by making software accessible, you also learn a lot about how you can simplify the software.
EHR Design Talk with Dr. Rick 1/23/12: Computer-Centered versus User-Centered Design Within the next few years, … bit.ly/yPqDOw
— histalk (@histalk) January 24, 2012
Dr. Rick does a great job starting the conversation around EHR usability. I can’t imagine the effort he put in just to create the first post. Of course, it is a first offering, but I’m really glad that he’s started a deeper discussion around EHR usability. My only disappointment is that he isn’t posting them on one of my sites instead of HIStalk. Regardless, by the looks of the discussion in that post it’s going to drive some really interesting conversation that will hopefully result in improved EHR design.