The Primary Care IT toolset is a suite of resources designed to optimise operations within General Practices. It consists of templates, alerts, protocols, and searches, all embedded within your existing electronic health records (EMIS Web, TPP SystmOne, etc). These resources, which are tailored to contractual and localised requirements, aim to make life easier for staff and improve patient care.
We understand that you might be curious about how these tools are developed and how long it takes. Let us explain our process and timelines, so you know exactly what to expect.
Our Development Process
Initial Assessment
Our team meet once a week to go through development requests. At this stage a decision is made to either take forward the request for further assessment or reject the request, then the customer will receive an email that informs them of the decision taken.
Awaiting development
Once the initial assessment has taken place, requests that have been taken forward are placed into a holding area where all ideas awaiting development are held. Each request is given a priority and our team review those that are at the higher priority level when they have capacity to take on additional new work.
High-Level Scoping
Once a decision to develop a request has been made we undertake a more detailed scoping of the requirement. This step involves analysing the contract or requirement, brainstorming how we can create the needed support across all systems we provide for, and understanding any questions that we need to ask of you, the customer. During this phase, we also estimate the build duration. This step usually takes about two weeks, but larger projects might require a bit more time.
Build Phase
The resources are then built during the Build Phase, which typically lasts 4-6 weeks. However, this timeline could change depending on the size and complexity of the project, and on the competing priorities that our teams are trying to balance during this time.
Quality Assurance
After the Build Phase, we undertake Quality Assurance to test the build quality and assumptions. This is performed by a second team member and typically takes about two weeks.
User Acceptance Testing
We then share the resources with end users during User Acceptance Testing. This phase, usually lasting two weeks, allows us to gather valuable input from a small focus group of engaged subscribers. If feedback suggests significant changes are necessary, we may need to return to the Build Phase.
Communication Resources Creation
Simultaneously, we spend two weeks creating communication resources, training videos, and support materials.
Go Live
Finally, we're ready to go live!
Communication During the Development Process
Regular communication is vital to ensure a smooth process. We maintain regular contact with the contract owner to update them on progress. If there are any unexpected changes or delays, you'll be the first to know.
Supporting You Throughout the Process
When rolling out a new tool, we're committed to providing comprehensive support resources. We launch the tools with a recorded webinar that walks you through the contracts and resources.
In addition, you'll find support articles and lessons within the Primary Care IT Hub, a section of our website dedicated to providing bespoke localised information.
Thank you for choosing the Primary Care IT toolset. We value your partnership and are excited to continue delivering tools that enhance your daily operations and patient care.
How to Raise a Development Request
If you wish to raise a development request for consideration by our development team, please raise a support ticket.