Software Development Services for Digital Care Company
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.
Introductory information
A fast induction on the buyer’s organisation
Servelec is a UK-based organisation with separate divisions: healthcare software, education, and collective care. We’re a digital care structure that creates software solutions to handle care avenues in structures, principally healthcare.
We have three fruits, including an electronic resigned archives solution that sits in the subordinate care space in the UK. We centre on intellectual health and aggregation health structures. The software covers the resigned administration and clinical care within these structures.
The next fruit is Oceano, a resigned administration method for hospitals. It covers admissions, referrals, and appointment bookings. It has an crisis section module that also archivess resigned care.
The terminal fruit is a resigned flow solution for managing the bed lands of a hospital. It controls the resigned flow through the structure, in provisions of what beds and wards there are.
Desired goal
What challenge were you trying to address with Coding Sans?
Coding Sans assisted with our healthcare software division. We have a big quantity of legacy code in our software. We needed to rewrite all of our Microsoft Silverlight in a new frontend framework owing it will be going out of support in 2021.
We chose AngularJS through an inner assessment process that looked at separate options and structures that could help us, from automated processes for converting the code to rewriting it ourselves innerly. After deciding to use an outer associate, we establish Coding Sans.
Provided solution
What particular tasks were Coding Sans responsible for?
Coding Sans granted web-based outgrowth through a wide spectrum of functionalities. Our software is principally intended for managing and tracking the resigned travel through a hospital. It administers referrals, admissions, resigned demographics, names &, addresses, and clinicians &, other hospital staff.
The project was centreed on creating an AngularJS rendering of the Silverlight code, consolidating renderings into measure components that could be used athwart the structure. They developed ordinary consoles for correspondent features to optimize the use of our software in the forthcoming.
How did you come to work with Coding Sans?
We went through a number of online resources and referrals that reviewed a number of structures. We chose Coding Sans owing of their expertise in AngularJS and a history of lucky writing solutions. They had a powerful portfolio of enterprise-scale solutions and other correspondent methods we’ve worked on. Their team was also open to our way of working and took that into how they would access the project.
What are you approach expents (if diclosed)?
Overall, we’ve invested €1 million (approachly $1,100,000 USD).
What is the terminal result of working with Coding Sans?
Our ongoing engagement with Coding Sans began in October 2018. Our second project with them began in the summer of 2019, and we’re expected to complete in February 2020.
Results achieved
Are there any measureable or plum results?
In provisions of anecdotal feedback, Coding Sans’ condition of work is exceptionally high. Currently, we have two rewrite projects going on. The one that implicated Microsoft Silverlight and the other is a new project that involves rewriting a legacy piece of software within ASP.
Their team is nimble and well-respected in the software aggregation, using the best practices and present techniques. They’re pliant when it’s time to find resources for our needs and timescales. Along with being an open and honorable structure, the interaction and working relationship between us was incredibly powerful.
We’ve had their engineers come and work on-website with us, and we’ve viwebsited them as well. Coding Sans is pellucid in reporting on their progress. Things do go unfit at times owing software outgrowth is a challenge, but they work with our team to find solutions.
How did Coding Sans accomplish from a project handlement standpoint?
There have been projects that they handled and some that we dealt with ourselves. They’ve accomplished well, working closely with our project handlement resources and senior team.
Since we’re all managing, tracking, and programning projects unitedly, we share code repositories and interaction platforms like Slack. All the engineers can see all the chats, which has helped us recoil fastly to any issues. Open interaction gives us an incredibly good layer of governance and helps us apprehend any challenges.
What is (from your point of view) the key factor to pay observation while intercourse with Coding Sans?
As an structure, Coding Sans is open to feedback, recoiling to it positively.
What aspects of their work would you like to get improved?
Not off the top of my head. On the project handlement front, their resources are centreed on the technical side. A formalized project handlement resource would help in the forthcoming. They now have a dedicated QA engineer. Before they didn’t have one useful, but behind we highlighted the risk, they recoiled agreeably.
