The Cutting Edge of Medical Technology Content, Community & Collaboration
Guest Article: "Selecting or Designing iPhone and Mobile Software for Physicians" ... The Healthcare IT Guy
Colleagues,
In the continuing quest to deliver the 3C's of "Content, Community & Collaboration", we are beginning to link to and/or feature "Guest Bloggers" producing insights we think you can use. This is the third recent blog from the "Healthcare IT Guy", Shahid Shah ... Here are Shahid's recent thoughts on "Selecting or Designing iPhone and Mobile Software for Physicians" ...
..... I get a lot of questions asking for advice on how to build mobile software and one of the most popular questions is about how and where to save data on a mobile device (because of HIPAA and privacy rules). I reached out to Adam Kenney, a software engineer pMDsoft who leads a team of developers focused on mobile charge capture. Adam and his team have been building medical apps for mobile platforms and his insights arise from direct experience managing the design, development, and support of native applications for the Palm, BlackBerry, and iPhone. Here’s what Adam wrote.
Any physician who spends time in the hospital setting understands the importance of “taking it with you”. Web-only software is great; but even now, when many hospital rooms have a terminal on hand, the overhead of logging in and logging off for each patient can be intolerable for busy physicians who are already spending too much time on administrativia.
This is where mobile software comes in. Doctors were among the first adopters of mobile devices such as Palms. With the rise of smartphones, and with government initiatives such as e-prescribing, mobile software is more appealing than ever. But it’s challenging to make software that fits the constraints of a mobile platform yet is fast, fun, and friendly to use; and only usability will allow you to save time and achieve 100% adoption within your organization.
One of the biggest factors in the usability of mobile software is how data gets onto and off of the device. Here are a few of the most common approaches that mobile software companies take, with the pros and cons:
Option 1: “What happens on the device stays on the device”
Option 2: “Your information is out there somewhere”
Option 3: “Your information is everywhere you are”
.... The important thing is to anticipate what it will really be like to use an application. Will it save time, or impose additional burdens on physicians? Will they love it, or want to throw their smartphones out the window? Taking the time to understand a solution well before you buy it can prevent headaches and remorse down the road.
Read the whole blog at: http://www.healthcareguy.com/index.php/archives/645
ENJOY!
CC
In the continuing quest to deliver the 3C's of "Content, Community & Collaboration", we are beginning to link to and/or feature "Guest Bloggers" producing insights we think you can use. This is the third recent blog from the "Healthcare IT Guy", Shahid Shah ... Here are Shahid's recent thoughts on "Selecting or Designing iPhone and Mobile Software for Physicians" ...
..... I get a lot of questions asking for advice on how to build mobile software and one of the most popular questions is about how and where to save data on a mobile device (because of HIPAA and privacy rules). I reached out to Adam Kenney, a software engineer pMDsoft who leads a team of developers focused on mobile charge capture. Adam and his team have been building medical apps for mobile platforms and his insights arise from direct experience managing the design, development, and support of native applications for the Palm, BlackBerry, and iPhone. Here’s what Adam wrote.
Any physician who spends time in the hospital setting understands the importance of “taking it with you”. Web-only software is great; but even now, when many hospital rooms have a terminal on hand, the overhead of logging in and logging off for each patient can be intolerable for busy physicians who are already spending too much time on administrativia.
This is where mobile software comes in. Doctors were among the first adopters of mobile devices such as Palms. With the rise of smartphones, and with government initiatives such as e-prescribing, mobile software is more appealing than ever. But it’s challenging to make software that fits the constraints of a mobile platform yet is fast, fun, and friendly to use; and only usability will allow you to save time and achieve 100% adoption within your organization.
One of the biggest factors in the usability of mobile software is how data gets onto and off of the device. Here are a few of the most common approaches that mobile software companies take, with the pros and cons:
Option 1: “What happens on the device stays on the device”
Option 2: “Your information is out there somewhere”
Option 3: “Your information is everywhere you are”
.... The important thing is to anticipate what it will really be like to use an application. Will it save time, or impose additional burdens on physicians? Will they love it, or want to throw their smartphones out the window? Taking the time to understand a solution well before you buy it can prevent headaches and remorse down the road.
Read the whole blog at: http://www.healthcareguy.com/index.php/archives/645
ENJOY!
CC
Views: 6
MedTechIQ VideoLibrary
Upcoming Events
© 2024 Created by CC-Conrad Clyburn-MedForeSight.
Powered by
