site-logo

Case Study

Micropathology Website

Micropathology is a private laboratory that provides rapid diagnosis to healthcare services across the UK.

Client

Micropathology Ltd

Coventry, UK

Project Duration

3 Months

2 People

Services

UI Design

Web Development

Client Challenge

Their old website suffered with outdated, non-responsive visuals and content. Due to the huge amount of rapidly changing information for clients, such as test lists, accredited samples and documents, it was difficult for staff there to keep it up to date.

This was being done by multiple people in different places, causing duplicated, outdated versions of data which was difficult to maintain.

The client needed a way to keep the content up to date in an efficient way.

Devising a Solution

Breaking it down

Instead of having staff manually update a text-filled table on the website, we decided to integrate it with their LIMS system. This meant that it displayed the tests that were already up to date for internal processing automatically and reduced data redundancy and human error.

Backend Approach

Data Cleansing

The test names that needed to be displayed on the website sometimes differed slightly to the names they preferred to go by in their LIMS system. This meant we had to create a few custom fields in the database specifically to handle website display. The LIMS was updated to handle these appropriately.

With clean data, we were able to add search features and remove the need for additional user input.

Additional Features

PDF Documents

Information sheets were maintained by scientists and had to go through strict document control procedures. With their previous website provider, it was always a challenge to get them uploaded promptly.

By integrating the website with their LIMS, we were able to build a feature which allowed the heads of each area to update the documents on the website in a few clicks.

Tecnology Approach

.NET Core

A number of their internal systems were already built in .NET and they had internal infrastructure to accomodate this.

We chose .NET Core because it provided the option for them to host their website in the cloud for high availability if they chose to do so in future while keeping in-line with their existing infrastructure as well as not requiring a learning curve for their internal development team.

Project Outcome