Body1
  • Solutions
    • BioPharma
    • MedTech
    • Private Equity
  • Services
    • World-Class Websites
    • Strategic Positioning
    • Tagline Creation
    • Project Management
    • Online Security
    • Physician Finder System™
    • Other Digital Solutions
  • Portfolio
    • Corporate Websites
    • Multilingual Sites & Translation Tools
    • Product Websites
  • About
    • About Us
    • Resources
  • Contact Us
  • Login
  • Search
  • Menu Menu

7 Deadly Mistakes which Kill Templated Medical Websites

July 9, 2014/in eCommerce, health, interactive marketing, Magento, medical content management, mobile, regulatory, social media, website templates, websites, WordPress /by Chris Messina

Templated sites from WordPress (WP), Magento, and others have become popular.   We at Body1 even deploy these for small healthcare clients launching their first sites.   They are cheap.  They are convenient.  And they can be dangerous.

Here are seven common mistakes that we’ve seen.  We’re often brought in to fixed “shattered” software projects, where a project starts and then cannot finish because of added complexity due to poor planning and unexpected scope creep.

1. Modifying a template without planning. Template-driven systems like WP or Magento are fine but customization adds considerable complexity.  Adding or deleting features changes the overall code base.  Separate parts of the site will break, suddenly incorporate random pieces of code, or reformat the page, among other unexpected issues.  To address this, Body1 systematically scans the entire site in a staging environment after every major code push, with the ability to selectively roll back and adjust potentially problematic changes.

2. Ignoring QC and testing.  The activities of quality control (QC) and testing actually are as important as coding.  Coding is only 50% of successful website or marketing software deployment.   Once a site is coded it has to be thoroughly checked and the code updated to fix issues.  This step is often skipped on templated sites- and then the owner is surprised when the site breaks.  Automated link checkers, load simulators, and browser emulators are useful tools.  On sites Body1 builds we use such tools to check issues prior to launching but inevitably there are still issues which can only be caught by a smart pair of human eyes.

3. Not deploying a separate “stage” site.  It’s easy to develop in a folder on the planned live site.   It’s harder to set up a separate, password-protected “staging” site with a process to cleanly copy the files over to the planned live site.  But that is best practice.   Completely separating the development from the live code ensures that:

  • all the functionality can be confirmed as working before deployment,
  • code in the development & live folders does not conflict, and
  • issues in deployment can be quickly and easily fixed.

4. Ignoring the hosting environment details.  Understanding and control of the hosting environment is critical to successful programming.  Issues in hosting often cause problems with the site performance that masquerade as software problems. This is why Body1 controls its hosting environment.  We were called by a panicked customer with a Magento site (eCommerce web template from eBay) whose log-on was failing and their “Magento programmer” couldn’t figure it out.  It turned out it was caused by the host running out of disc space (see below).  Without disc space the programs will fail.  This was especially acute for this eCommerce site where there was a 4gb catalog and multiple development folders.

5. Hiring a low cost developer to start with a quality development team on stand-by.   This is the classic “penny-wise, pound-foolish” trap.   Coming in to clean-up in a crisis situation is not ideal for anyone.   Starting with a low cost developer (often one with heavily discounted rates who works out of state or overseas but is “always available via Skype”) is a sure way to slow or break your website.  Such a process also ensures that a high quality development team will have to be brought in at the last minute, on a rush basis, to decipher code and re-architect a site under intense deadlines.  Since it is always more complex and takes longer to unravel someone else’s code, problems are invariably missed.  This results in the development process being more time consuming and expensive.

6. Retaining the cheap talent to work on perceived “easy parts” of the website while the top talent fixes the problems.  This is the classic “Too many cooks in the kitchen spoil the broth” situation.  We’ve seen firms do this to try to reduce costs on shattered projects.   However it inevitably ends up not being cost-effective as the coordination needs increase significantly and the coding efforts end up conflicting.  If the project is “shattered”, the cheap outsourced programmer costs, rather than saves, money.  Using a top development firm on a templated site facilitates control of the hosting environment, properly staged projects, and leverage of automated testing tools and QC.

7. Eschewing site monitoring and maintenance after launch.   A templated site is not a high-availability site, nor is it fool-proof site.  Automated monitoring and planned on-going maintenance of websites is valuable.  This is especially so for healthcare sites.  Automated monitors can detect problems before they before obvious to the end user.  Monitors even can be set up that follow every order through the purchase funnel for sites selling health products or services.  Besides real-time QC, those monitors then provide a tool to analyze consumer buying behavior.

Maintenance plans allow these problems to be fixed proactively without impacting the their live environment.  Because web browsers (such as Explorer, Chrome, Safari, and Firefox) and operating systems (such as Windows, OS, and Android) evolve, it is inevitable that the unmaintained templated website will break.  A good rule of thumb is to allocate 20-25% of an initial web budget to ongoing maintenance.

Avoiding the 7 deadly mistakes of templated medical websites is not hard.  A little forethought, a dash of prudence, and the willingness to invest initially is the best way. Besides on time and on budget website launches, there is an added benefit- maintaining one’s own emotional equilibrium.

Chris Messina

https://body1.com/wp-content/uploads/2018/12/Body1-newlogocolored.png 0 0 Chris Messina https://body1.com/wp-content/uploads/2018/12/Body1-newlogocolored.png Chris Messina2014-07-09 10:20:092018-04-18 19:10:227 Deadly Mistakes which Kill Templated Medical Websites

Gene Tests, Delivery Drones, & Avoiding Regulatory Meltdowns on the Web

December 6, 2013/in eCommerce, genomics, health, interactive marketing, leadership, medical content management, mobile, regulatory, social media, websites /by Chris Messina

There are some interesting parallels in the FDA’s recent action telling the firm 23andMe to “cease & desist” all marketing of its personal genomics test with the recent news about Jeff Bezos and the Amazon “delivery drones”.  Both are new technologies which will require regulatory understanding and adaptation.

However, by contrast, Amazon has floated (figuratively & maybe literally…) the drone idea, launching public discussion and regulatory contemplation.  By contrast, 23andMe blazed ahead.  Brave? Hubristic? Both?

The FDA’s approach is almost always to prioritize the prevention of harm.  Is there potential harm (like unnecessary prophylactic organ removal) from misinterpretation? Probably.  Can it be mitigated?  Surely, but the FDA will want to be part of crafting the solution if it’s potentially accountable for the potential harm.

My experience running an orthopedic device firm taught me that firms consult with the FDA retroactively at their peril. Even now it is surprising how few medical & wellness firms have a regulatory control process in place for public-facing web content and mobile apps.

What are the practical lessons here?

  1. Both are new technologies, which will require regulatory understanding and adaptation.
  2. Both are best served by proactive vs. reactive regulatory engagement
  3. Amazon has approached the regulatory environment more cleverly by “floating” its idea early.
  4. It’s possible to re-engage after facing regulatory problems, but more difficult.
  5. Inadequate or missing systems for regulatory content management is another area where many firms fail.

I hope 23andMe works things out with the FDA. It would have been far better to fully engage them earlier, but there is still hope.

Chris Messina

https://body1.com/wp-content/uploads/2018/12/Body1-newlogocolored.png 0 0 Chris Messina https://body1.com/wp-content/uploads/2018/12/Body1-newlogocolored.png Chris Messina2013-12-06 15:43:112018-04-18 19:10:30Gene Tests, Delivery Drones, & Avoiding Regulatory Meltdowns on the Web

Recent Posts

  • MedTech
  • Design
  • Serious New Security Issues (Meltdown/Spectre) and How to Address Them
  • Cyber Security and Spam: How to Protect Your Website from Attack
  • Can the Compassion of “The Crowd” Reduce Suicide?

Archives

  • September 2019
  • December 2018
  • January 2018
  • December 2015
  • November 2014
  • July 2014
  • December 2013
  • September 2012
  • May 2012

Categories

  • Analytics
  • chronic conditions
  • Content Creation
  • cyber security
  • digital apps
  • doctors
  • eCommerce
  • genomics
  • health
  • interactive marketing
  • international
  • leadership
  • Magento
  • medical content management
  • mobile
  • Physician Finder System
  • Project Management
  • public health
  • regulatory
  • Security
  • social media
  • spam
  • suicide prevention
  • Uncategorized
  • website templates
  • websites
  • WordPress

Home          Solutions          Portfolio          About          Contact

                    

Home
Solutions
Portfolio
About
Contact

                    

Scroll to top

This website uses cookies for functional and analytical purposes.

Opt InOpt OutLearn more

Cookie and Privacy Settings



How we use cookies

We may request cookies to be set on your device. We use cookies to let us know when you visit our websites, how you interact with us, to enrich your user experience, and to customize your relationship with our website.

Click on the different category headings to find out more. You can also change some of your preferences. Note that blocking some types of cookies may impact your experience on our websites and the services we are able to offer.

Essential Website Cookies

These cookies are strictly necessary to provide you with services available through our website and to use some of its features.

Because these cookies are strictly necessary to deliver the website, you cannot refuse them without impacting how our site functions. You can block or delete them by changing your browser settings and force blocking all cookies on this website.

Google Analytics Cookies

These cookies collect information that is used either in aggregate form to help us understand how our website is being used or how effective our marketing campaigns are, or to help us customize our website and application for you in order to enhance your experience.

If you do not want that we track your visist to our site you can disable tracking in your browser here:

Other external services

We also use different external services like Google Webfonts, Google Maps and external Video providers. Since these providers may collect personal data like your IP address we allow you to block them here. Please be aware that this might heavily reduce the functionality and appearance of our site. Changes will take effect once you reload the page.

Google Webfont Settings:

Google Map Settings:

Vimeo and Youtube video embeds:

Privacy Policy

You can read about our cookies and privacy settings in detail on our Privacy Policy Page.

Privacy Policy
Accept settingsHide notification only