Skip to main content

Telemedicine market to reach $2.5B by 2018 | Healthcare IT News

LONDON ? The thriving telemedicine market hasn't shown signs of abating any time soon, according to a new report by Companies & Markets. The report shows that in 2011, the global telemedicine monitoring market reached a value of $736 million and, according to officials, is poised to increase to $2.5 billion by 2018.

This significant growth in the global market can be attributed to numerous factors as telemedicine monitoring provides ways to improve clinical care delivery to patients while also reducing the need for hospitalizations and visits to the emergency room.

[See also: Telemedicine burgeoning in BRIC countries.]

Telemedicine is the use of telecommunication and information technologies in order to provide clinical healthcare at a distance. It helps to eliminate barriers and improve access to medical services that would often not be readily available in rural communities. The technology can also be utilized in critical care and emergency environments.

Having the ability to accurately access patient condition via a combination of advanced testing and telemonitoring creates the opportunity to intervene during a clinical emergency and permits education provisions regarding healthy living in a way that is likely to create compliance with clinician recommendations.

[See also: Telehealth boosts ICU for rural hospitals.]

Telemedicine table devices typically cost $350 in 2011, with the average price of the software at $75 per unit. Officials say this indicates a growing services business that will pay for the devices over time.

Moreover, telemedicine has been seen to be beneficial for individuals living in isolated communities and rural regions. Telemedicine technology allows patients who live in these rural areas to be seen by a doctor or specialist, who can provide an accurate and complete examination, without the patient to traveling away from their families to far-off medical centers.

To access the Companies & Markets telemedicine report, click here.


via healthcareitnews.com

Interesting news. I would love to see remote diagnosis and treatment in areas like occupational therapy using Kinect like tools :-)

Labels:

Comments

Post a Comment

Popular posts from this blog

Creating star ratings in HTML and Javascript

I'd searched around a little for some shortcuts to help in doing this but I couldn't find anything satisfactory that included the ability to pull the rating off again for saving. I'd ended up coming up with this rather cheeky solution. Hopefully it helps you too! This is my first post in a while (I stopped blogging properly about 8 years ago!) It's strange coming back to it. Blogger feels very crusty and old by todays standards too.
Post a Comment
Read more

Make your objects immutable by default

More about the Good Dojo In my post last week , I discussed creating objects that are instantiated safely. Please go back and read if you are interested. At the end of the post, I mentioned that I'd also written the class so it was immutable when instantiated. This is important!!! I feel like a broken record in repeating this but I am sure at the time of writing your code, you aren't modifying your object all over the place and so are safe in the belief that protecting against mutability is overkill. Please remember though, your code could be around for a hell of a long time. You aren't writing your code for now... you are writing for the next fool that comes along (including you) . Nothing is more upsetting that coming back to fix a bug on some wonderfully crafted code to say "Who has butchered my code?!", but often you were involved at the start of the process. You made the code easy to modify, allowing objects to be used / reused / modified without thi
Post a Comment
Read more

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second
Post a Comment
Read more