TWO TRUTHS AND A LIE – LEGACY THREE TIER ARCHITECTURE AND THE CHANGING NEEDS OF ENTERPRISE IT

2017-07-27T00:01:00+00:00 April 30th, 2015|News|

April 30, 2015 – Traditional datacenter three tier architectures cover a large percentage of your company’s current datacenter footprint.  These tiers are comprised of three core components: server, storage, and network. These three tiers work in tandem with one another to make sure your applications, end-users and business processes can perform without interruption. But in order to maintain a smooth work-flow, your IT department must support this three tier compute and storage architecture, often times requiring large teams of workers with specific skill sets to keep each individual tier functioning properly.

The downfall of this legacy three tier system becomes very evident, however, during times of business growth. Instead of your IT department functioning as a strategic asset to make growth more possible, your legacy systems require you to refocus all your valuable IT assets towards making the laborious additions to your systems.

Here are two truths and one lie that every IT department must face when your company is experiencing a time of growth:

 

Truth #1: Relying on your legacy three tier compute and storage architecture to support your company’s new or growing virtualization needs will cost you money, productivity and time.

What really happens when your company experiences growth? Say your legacy three tier compute and storage architecture is built to handle 1000 users, but you’re already at capacity. Your CEO lets you know that 100 new users need to be added, and expects this to be done quickly.

In truth, each tier must then be modified individually to execute those growth needs successfully. This can be a lengthy, time consuming process, and extremely expensive. Your CEO will not be pleased with this slower time to start or additional costs that impact the overall budget, even if the adjustments are beyond your control.

Our advice: Research the term “Hyperconvergence” and “Hyperconverged Datacenter”. What you’ll find is a new approach to these current IT complexities. Hyperconverged Architectures allow you to grow at any pace needed, without sudden unexpected costs or productivity delays.

 

Truth #2:  Legacy three tier compute and storage architectures usually require large teams of high cost skill sets for each of the three tiers.

In a typical three tier architecture, you have to develop the specific skill sets around each component. You need IT staff members with the expertise to manage your physical and virtual server workload, design, maintain,  and optimize your storage environment, and provide the skill set required for the ever changing needs of your network architecture.

While these are valuable assets to your department, they would be better suited for new and emerging projects instead of being weighed down with constant menial maintenance tasks.

Our advice: Minimize the soft HR costs that are required to support these teams and invest in a Hyperconverged Datacenter that can manage two of those tiers in one, without all the technical expertise required.  This software defined datacenter approach will allow your skilled team members to focus on IT initiatives that will propel your business into a more competitive realm. It will also improve productivity and time to market for new business solutions and systems.

 

The lie is that you can continue to invest expensive and long procurement and implementation timelines of legacy three tier architectures while simultaneously providing your business the advantages of Hyperconvergence.

 

Having a Hyperconverged Datacenter strategy and collapsing the compute and storage tiers into a unified, easy to manage environment cuts down on space and maintenance costs of a traditional architecture. Adopting Hyperconvergence will also allow your business to increase agility and the ability to scale quickly, as well as creating a more stable, solid platform to meet a large portion of your current business needs.  Instead of taking months to acquire, set-up and configured legacy infrastructure, you can provide an environment ready to receive your virtual workload in as little as 2-3 weeks. Business won’t be delayed and project expectations can be exceeded. As the business world moves forward with this new cutting edge datacenter technology, make sure you’re providing your company the opportunity to stay ahead of the curve.

HOW TO RECOGNIZE POOR END USER ISSUES BEFORE THEY BLOW UP – FOUR KEY INDICATORS TO WATCH OUT FOR

2015-12-29T18:24:04+00:00 April 30th, 2015|News|

April 30, 2015 – As an IT leader, you are the most influential decision maker in your organization when it comes to IT solutions. Yet paradoxically, you may also feel the furthest away from the end users who are utilizing your solutions. What does this mean? Often, this translates to a feedback lag – by the time you hear about the problems your end users are experiencing in clinical environments, the issues have escalated and are already seriously impacting workflow, clinical care, and patient satisfaction.

So, how do you proactively manage the end user experience and avoid clinician frustration and lost revenue? It’s simple: by recognizing poor end user issues before they blow up in your face. Don’t wait for a crisis during EMR implementation or a HIPAA violation to investigate.

 

Here are four key indicators of a poor end user experience to watch out for:

 

1. Your physicians won’t stop talking about it.

Your clinical team members are motivated by providing excellent patient care, and the more time they spend navigating through inefficient virtual environments, the more frustrated they get. The most vocal group is most likely your physicians, many of whom feel mandated to use computers and may not be technologically savvy. More screen time means less patient time, and less revenue. If you’re hearing complaints and frustrations from your physicians, it’s time to address the issue.

 

2. It’s taking more time to see fewer patients.

If your healthcare system end users are using kiosk devices with generic windows logons or are doing a full windows login every time they access a clinical device, it’s taking them more time to access – and navigate – their critical applications. Are your clinicians constantly on the phone with field services technicians customizing endpoints and trouble-shooting? Then their workflow isn’t optimized. This translates to more screen time and less touch time with fewer patients. This has a direct impact on patient satisfaction, discharge times, and, ultimately, your revenue.

 

3. Physician referrals are off, and you can’t figure out why.

Physicians will refer patients to hospitals and providers that make it easy for them to do so. If working within your Health System is more time consuming and complex than at your competitor’s Health System, the physician is going to refer their patients where they can do their work in the least amount of time and with the least amount of complexity.  It’s that simple.

 

4. Patient satisfaction scores are down.

Too much time spent accessing or working in front of a computer means that patient wait times are longer across the board – from waiting room to exam room – which leads to frustration and dissatisfaction. The less one-on-one time patients have in their healthcare experience, the less connected they feel. Your reputation as a patient-focused provider is negatively affected, and this impression can easily be attributed to your entire health system. If your patient satisfaction surveys have shifted, take notice.

 

The above mentioned red flags are clear indicators that your clinical workstation infrastructure is not efficient or effective, and the effects can trickle down through every level of your organization. Most importantly, consider the benefits of recognizing poor end user issues before they blow up: motivated physicians, efficient clinical care, faster discharge times, consistent referrals, increased patient census and revenue, and a reputation for the highest standard in state-of-the-art patient care.

Server 2003 EOS, Part 5…

2017-07-27T00:01:00+00:00 April 1st, 2015|Uncategorized|

(Please see Server 2003 EOS Parts 1, 2, 3, and 4 for background)

Wow, we’re at the end of our 4-part series of webinars about the Comfort Trap of Server 2003, and the End of Service.  We’ve covered a lot over these sessions, and shared some great insight and detail about various challenges you face — and options you have — in getting your critical services off of Server 2003.

I want to thank Avi for his help and contributions to this episode, where he brings his skills and background as a developer and application specialist to help us understand the complexities of the application space.

And while today is April fool’s day, it’s no joke that some of your critical systems may be at risk when support ends on July 14th.  Interestingly, today is 4/01 and the Server 2003 EOS is just 104 days away as I type this…

So kick up your feet and relax, and spend about 42 minutes with us.  It’s just what you need to get out of the Comfort Trap!

By the way, our other sessions can be seen here:

Thanks to all that attended the live webinars!  We’ll keep you posted on future items and events, and look forward to hearing from you…

 


Fatal error: Uncaught exception 'GuzzleHttp\Exception\ClientException' with message 'Client error: `POST https://dc.services.visualstudio.com/v2/track` resulted in a `400 Invalid instrumentation key` response: {"itemsReceived":1,"itemsAccepted":0,"errors":[{"index":0,"statusCode":400,"message":"Invalid instrumentation key"}]} ' in /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113 Stack trace: #0 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Middleware.php(66): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response)) #1 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(203): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response)) #2 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(156): GuzzleHttp\Promi in /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113