Archive for April, 2012


Rooting Your Android Tablet: Pros/Cons

Posted on: April 24th, 2012

Android tablets are quickly becoming the go-to tablet for companies and manufacturers. The openness of the OS and the ability to personalize it has major appeal. If you have an Android tablet, or have been reading about them you have probably come across the term “root”. If you’re not quite sure what this means for you and your tablet, we’re here to help.

Before you root your tablet it’s beneficial to know the pros and cons associated with it.

What is Rooting? When you buy an Android tablet, it will have limitations placed on the OS by the maker of the tablet to prevent inexperienced users from inadvertently ruining their device. What rooting does is give users access to the basic or “root” level of the tablet, in other words it removes all restrictions placed on the OS. If you’ve heard the term “jailbreaking” for Apple’s products, rooting is akin to that.

Benefits to Rooting There are a number of upsides to rooting your Android tablet. Some of the most positive features are:

  • Access to More Applications. If you root your tablet, you’ll have access to a wide variety of apps not available to unrooted tablets. If you go to the Google Play store, and type in Root you’ll see a list of apps that are only available to rooted tablets. Some of the most useful include ones that allow you to do a full backup of your system or change your layout.
  • Improved Performance. When you root your tablet, you’ll be able to control its performance. This includes being able to make it open and close apps faster or decrease processor speed which will increase battery life.
  • Latest Version of OS. Companies that create tablets and devices that use the Android OS are notorious for taking a long time to update the OS. Case in point: Google released Android 4.0 in December 2011 and some devices still haven’t been upgraded. If you root your tablet, you’ll be able to update your device to the newest version of the Android OS by using a ROM - the most basic level of software that allows your Android device to operate. ROMs are akin to drivers used by computers.
Drawbacks to Rooting There are some drawbacks to rooting that you should be aware of. The first issue is that if you do root your tablet, the warranty will be voided. If the manufacturer finds that you’ve rooted your device, they could refuse to fix it, forcing you to go to less than reputable dealers.

The second problem is that if rooting is carried out incorrectly you run the risk of “bricking” or “bootlooping” your device. Bricking is when your tablet’s software glitches causing the tablet to stop working, making it about as useful as a brick. Bootlooping is similar to bricking, however your phone will boot up, turn off, boot up and turn off in an endless cycle.

The final downside to rooting is security. There has been an increasing number of malware apps designed specifically for Android devices. If you have a rooted tablet and download apps not from Google Play, there’s a higher chance that the app you download will be infected.

Should I Root? With both powerful benefits and potentially nasty problems, the question is, “Should you root your tablet?” The answer is a bit ambiguous in that it really depends on what type of user you are. Advanced users who want to micromanage their device will be able to do just that if they root, while users who are happy with their tablet will not see much of a difference.

If you do choose to root your tablet, search the Internet for guides on how to root your device and carefully follow the instructions. Should you like to learn more about rooting, or Android tablets please drop us a line, we’re more than happy to hear from you.

Published with permission from TechAdvisory.org. Source.

Integration Capabilities Your EMR Needs

Posted on: April 17th, 2012

With the adaptation of Stage 2, companies operating in the electronic medical records will shift their focus from the capture to exchange of health information. One industry insider has recommended 10 things your EMR needs to be truly interoperable.

  1. Single sign-on (SSO). Applications tend to proliferate, and if you don't allow people to switch between these applications using a common login and password, users will get frustrated and give up.
  2. Context transitions. As applications grow, and you need to integrate them into an EMR, SSO won’t be enough, because you’ll still lose the “active patient or task" being performed. You’ll also need to provide for the transition of context between applications.
  3. Widget publishing. EHRs often have hundreds of functions, and if some are exportable or publishable as widgets, they become much easier to integrate into new user interfaces in the future.
  4. Widget consumption. EMRs will become more like containers of cross-application functionality than innate functionality, so consuming widgets will be a basic requirement.
  5. Mash-ups. EMRs should allow access to their content through the content management interoperability services (CMIS) standard, thereby allowing users to unlock content they have in various health records.
  6. Customizable dashboards. EMRs should provide dashboards that can be tailored by organization, user role, or even user.
  7. Interactive Voice Response (IVR). IVR, which allows an EMR to interact with users through phones and other voice systems, such as Skype, will improve collaboration with patients and other physicians who aren’t at a computer.
  8. Voice recognition. This will help users conduct EMR tasks more efficiently.
  9. Natural language understanding. Because most EMR data is entered by humans, an EMR must integrate with systems that can convert the spoken word or typed text to structured data.
  10. Customizable data import and export. A good EMR must allow customizable importing and exporting of simple lists in common formats, such as Excel, CSV and XML.
Details about these tips, and an additional two not discussed above, can be found here.
Published with permission from TechAdvisory.org. Source.

Creating a Strategic IT Plan – Five Tips

Posted on: April 17th, 2012

In order for your IT department to be successful, you need a strategic plan that will both optimize your workflow and help to define your practice’s needs. The well thought out and executed plan will exhibit a focus on the experiences of your staff and patients. Here are five considerations that can help you develop your strategic IT plan.

  1. Improve the patient experience. Many healthcare practitioners consider the patient experience a major challenge, yet don’t give much thought to how IT can improve it. Consider what you can do electronically to support patients, whether they're in your facility or not. Electronic forms? Email and text message reminders and confirmations? Kiosks?
  2. Consider best practices. Technology can help you get to know your patients better. The Web, for example, can be used as a first point of engagement. Ask a few questions of visitors, then tailor your responses to their needs. A patient interested in a first consultation would receive different information than one preparing for his or her first round of cancer treatment.
  3. Don’t forget the staff! Your staff needs successful workflows to interact effectively with patients. Common errors are multiple devices and different logins. Keep in mind how clinicians work to develop efficiencies. Your staff needs to be able to provide clinical care without being tied to a PC.
  4. Use social media. Social media often isn’t included in IT planning, as it’s usually more of a marketing consideration. Without thinking about how it will be used, it will become difficult for patients and staff to have a singular experience. Your IT department needs to work with other departments to develop a social media plan that will yield a consistent presentation to the end user.
  5. Use integrative planning. Typically, IT does its strategic planning in isolation. Ideally though, IT would plan with other departments. This “integrative planning” allows for a consistent plan supported by all parts of the practice.

Published with permission from TechAdvisory.org. Source.

Continuity Plan: Software or Templates?

Posted on: April 12th, 2012

With the increasing severity of natural disasters in recent years, many larger companies have started to develop and implement a continuity plan to ensure that they can still conduct business, no matter what happens. Businesses in the process of developing a plan will eventually need to decide if they want to use software or templates?

The decision between templates and software can be a tough one to make, as whichever one you choose, you’ll be using and relying on for a long time. To help you we’ve covered some pros and cons on both choices:

Using Software If you choose to go with a software program, you will be walked through the whole process allowing you to develop a useable plan. Another benefit of using software is that you’ll be able to develop reports if needs be.

The drawbacks of using software include cost, inflexibility and learning time. For the most part, business continuity planning software is not cheap, and at times can be inflexible due to limits within the program. If you have a niche need, the software may not cover it. In addition, as with mastering any program, the learning curve can be quite steep.

In general, using software would be advantageous for companies that have a bigger budget for the development of a continuity plan. Software is also a good bet if you don’t have staff who are experts in continuity planning, or if you operate in an industry where a continuity plan is necessary, e.g., companies working with healthcare insurance, or manufacturing companies that have introduced ISO 9000.

Using Templates If you feel that your company is not ready for software you can use templates to help you develop your plan. These solutions are mostly written plans that you adapt to meet your business needs. They’re useful if you’re just starting to do continuity planning, as they provide a normally solid foundation, and are generally a lot cheaper than software.

A limitation to using templates is that they can be a little too basic at times, and may not meet your needs. Granted, most plans will follow a basic structure and your developer will need to adapt some steps for your relevant region and industry.

As each industry is different, it’s hard to make a recommendation on what type of planning style companies should take. We recommend you take your time, do your due diligence and weigh out what’s best for your business. No matter which method you choose to go ahead with, ensure that it’s easy to implement, and that you’ll be able to teach your staff how to run the plan.

If you feel really lost or are not sure what to do, talking to professional consultants could go a long way in helping you develop a plan. If you’d like to learn more about business continuity planning please contact us - we are happy to help.

Published with permission from TechAdvisory.org. Source.

Watch Out! Cloud & P2P Security Risk

Posted on: April 11th, 2012

In the past five years, there has been a significant rise in the sharing of files and information between computer users. Many businesses have also taken to sharing files using cloud services and peer-to-peer (P2P) networks, allowing users to share files with each other over the Internet. This brings about a number of issues, both with file recoverability and overall security.

With the seizure of a number of cloud storage and sharing websites, including Megaupload, and the seemingly omnipresent malware in P2P files and the shaky security in relation to P2P networks, businesses have had their hands full staying secure. Do you know what your options are when it comes to data security?

Cloud Services Knowhow The recent seizure of Megaupload’s files and servers by the US Government caught many people and businesses unprepared. While Megaupload’s main purpose was file sharing, it was found that a large number of organizations were using their services to store files. If you had files stored on Megaupload, the chances of getting the files back are non-existent.

It needs to be pointed out that many cloud services don’t guarantee that files stored on the service will be recoverable in the event of a crash, or disruption in service, e.g., a government seizing servers. If you read the user agreements of a number of major cloud services, they all have clauses stating that if data stored on their service is lost for any reason, it’s gone forever, and the hosts can’t be held liable for losses.

Risks of P2P With high speed Internet widely available at low prices, P2P file sharing has become incredibly popular, it’s almost uncommon to find someone who has never used a P2P service. If you or your employees use P2P at your office, there are a number of potential security threats you should be aware of:

  • The unknown share: If you put a file in a folder that is shared on a P2P network, it’ll be shared with all other people connected to that folder and almost anyone can access it. This is normally done by mistake, i.e., not looking where the file will be saved when you save it. There’s also malware out there that will move files into a shared folder which the developer of the malware can find and upload with ease and without the user knowing it is happening.
  • Open network: Typically P2P works on open networks: users give and share. What this means is that when using P2P on a poorly configured network, the whole network could be unsecure, allowing for access to other computers connected to the network.
  • Untracked data: If you share a document with another person, and they then share it with others, there is potentially, an unlimited amount of people that can get the data. If you want to take it back, it can be impossible to do so, even if the original document is deleted.
  • Storage hijacking: There’s news of malware that has been developed with the purpose of downloading illegal material onto your hard drive. This could pose a problem if the data is found, as you will be liable.
What Should I do? With regards to cloud services, as with anything that comes with a contract, the first thing you should do is gain an understanding of it by utilizing reading material such as blogs, news articles and Wikis. It’s a pain in the neck, but it’ll help you understand the boundaries of the program and your responsibilities. Remember that if you go to court to get files back from a company, and it becomes known that you didn’t read the agreement, you’ll probably end up losing that case.

Second, it’s not recommended to keep single copies of data on one cloud service. Chances are high that in your business, you store your data and backups in a place separate from the computer. This makes sense with the cloud as well - keep your data with a number of different cloud services. If it’s important enough, have physical backups of what you put in the cloud.

For P2P networks there are also a number of steps you can take to protect the data on your network:

  • The most obvious one is to ban employees from using any file sharing services outside of your network.
  • If you do allow file sharing, it’s a good idea to establish and strictly enforce a protocol for this. You should also set which users are allowed to share files, and what files are appropriate to share. Be sure that all staff are aware of your policy and the measures that will be taken in the event of any deviations.
  • Develop a system to classify documents by whether or not they can be shared, and who they can be shared with.
  • If you work in an office where you need to share files, but don’t want to use a P2P network or the cloud, and are unsure of other solutions out there, don’t worry. There are companies that specialize in document sharing solutions that should be able to provide you with assistance.
The most important thing is that whatever the situation is, you take action to try to solve the problem while frequently revisiting the actions to ensure that they are working. If you’d like to learn more about document sharing over the cloud, or via P2P networks, give us a buzz. We’re more than happy to help.
Published with permission from TechAdvisory.org. Source.