By using this site, you agree to the Privacy Policy and Terms of Use.
Accept
Health Works CollectiveHealth Works CollectiveHealth Works Collective
  • Health
    • Mental Health
  • Policy and Law
    • Global Healthcare
    • Medical Ethics
  • Medical Innovations
  • News
  • Wellness
  • Tech
Search
© 2023 HealthWorks Collective. All Rights Reserved.
Reading: Do’s and Don’ts of Hospital Health IT
Share
Notification Show More
Font ResizerAa
Health Works CollectiveHealth Works Collective
Font ResizerAa
Search
Follow US
  • About
  • Contact
  • Privacy
© 2023 HealthWorks Collective. All Rights Reserved.
Health Works Collective > Business > Hospital Administration > Do’s and Don’ts of Hospital Health IT
BusinessHospital Administration

Do’s and Don’ts of Hospital Health IT

ShahidShah
ShahidShah
Share
4 Min Read
SHARE

 

Last year I started a series of “Do’s and Dont’s” in hospital tech by focusing on wireless technologies. Folks asked a lot of questions about do’s and dont’s in other tech areas so here’s a list of more tips and tricks:

 

Last year I started a series of “Do’s and Dont’s” in hospital tech by focusing on wireless technologies. Folks asked a lot of questions about do’s and dont’s in other tech areas so here’s a list of more tips and tricks:

More Read

doctor-patient relationships
The Doctor-Patient Relationship of Today
Should You Give Up on ACOs?
Sowing the Future Wearables Fields
Pick a Horse and Other Sage Advice About Leadership Decisions
Time for FDA to Hire Some Pharma Marketers?
  • Do start implementing cloud-based services. Don’t think, though, that just because you are implementing cloud services that you will have less infrastructure or related work to do. Cloud services, especially in the SaaS realm, are “application-centric” solutions and as such the infrastructure requirements remain pretty substantial – especially the sophistication of the network infrastructure.
  • Do consider programmable and app-driven content management and document management systems as a core for their electronic health records instead of special-purpose EHR systems written decades ago. Don’t install new EHRs that don’t have robust document management capabilities. Do consider EHRs that can be easily integrated with document and content management systems like SharePoint or Alfresco.
  • Do go after virtualization for almost all apps – as soon as possible, make it so that no applications are sitting in physical servers. Don’t invest more in any apps that cannot easily be virtualized.
  • Do start looking at location-based asset tracking and app functionality; your equipment should be aware of where it’s physically sitting and be able to “find itself” and “track itself” using location-based awareness. Don’t invest heavily in systems that can not support location-based awareness (like potentially allow or disallow logins based on where someone is logging in from as well as enable / disable certain features in applications on where logins are occurring).
  • Do start implementing single sign on and common identity management with CCOW integration. Don’t invest in any systems that cannot meet common identity or SSO requirements.
  • Don’t make long-term decisions on mobile app platforms like iOS and Android because the mobile world is still quite young and the war between Apple, Microsoft, and Google is nowhere near being resolved. A platform that looks strong today may be weak tomorrow and become legacy quickly; however, HTML5 is not going anywhere and will be ultimate winner of the next 15 years just like HTML4 is the winner from 1995 to now. Do start investing in HTML 5 and CSS3 and away from HTML4. Don’t install any more apps that require IE6/7 or older browsers and don’t invest in systems that don’t have HTML5 in their roadmaps.
  • Don’t write applications on top of legacy EHR platforms; write applications with proper HL7 connectivity and platform independence. Most EHR platforms are using technologies that are either ancient or need to be replaced; by integrating deeply but remaining independent of their technologies you’ll get the best of both worlds.
  • Don’t buy any medical devices from vendors that don’t have a deep and thorough medical device to healthcare IT enterprise connectivity strategy. If a device doesn’t have wired or wireless TCP/IP access, doesn’t have data export or HL7 connectivity is not worth purchasing.
  • Don’t buy any thick-client applications that do not have thin-client “remote viewers” available.

Share This Article
Facebook Copy Link Print
Share

Stay Connected

1.5KFollowersLike
4.5KFollowersFollow
2.8KFollowersPin
136KSubscribersSubscribe

Latest News

fight againt cancer
Breakthroughs in RNA Sequencing Provide New Insights in the Fight Against Cancer
Cancer News Specialties
February 1, 2026
aging in modern healthcare
Why Aging in Place Is Becoming a Cornerstone of Modern Healthcare
Global Healthcare Senior Care
January 29, 2026
Mental Health EHR
What Are the Core Features of a Mental Health EHR?
Mental Health Therapies
January 28, 2026
ADHD in adulthood
ADHD In Adulthood And Its Lasting Effects
Health
January 27, 2026

You Might also Like

Why Health Care Costs Are So High. Docs Don’t Know What Things Cost

May 19, 2011

Would You Trade Places with Your Physician?

January 28, 2014
Drug Seeker Or Pain Patient? Preparing Your ER For Frequent Flyers
DiagnosticseHealthHospital Administration

Drug Seeker Or Pain Patient? Preparing Your ER For Frequent Flyers

March 21, 2018
analytics reduce hospital readmission rates
BusinessHospital Administration

How to Use Analytics to Improve Readmission Rates

October 29, 2014
Subscribe
Subscribe to our newsletter to get our newest articles instantly!
Follow US
© 2008-2025 HealthWorks Collective. All Rights Reserved.
  • About
  • Contact
  • Privacy
Go to mobile version
Welcome Back!

Sign in to your account

Username or Email Address
Password

Lost your password?