Training and Education
Program Delivery In Health Care - Essentials (C2)
Understanding the V Model
At JDI Digital Transform, we aim to dispel the myth that implementation in health and life sciences is daunting.
While validation requires effort, it embodies good change practice.
When understood, it offers clarity and accountability for project requirements and solution design, ensuring thorough testing and risk assessment.
Our course provides an overview of the V Model to inform you how to integrate this into your costing and planning., forging better alliances and methods for working with your discerning Health Care Clients.​
1
Scary or just common sense?
Stripped back to its basic purpose, the V Model ensures:
-
Business stakeholders are clear and accountable for the Solution they want at line by line level
-
Solution Implementers and/or licence providers are accountable to deliver against those requirements at a line by line level
-
The Design, Build, Test phases retain the line by line scrutiny throughout the program life-cycle, to ensure this stays in synch
-
Testing and Risk assessment is thorough, evidence based and contemporaneous
​
Prior to deployment two documents are produced for the client which report:
-
if they got what they asked for? and
-
is it Compliant and Safe?
If question two answers 'yes' then deploy, if 'no' the project cannot go into production.
While seeming very Command and Control, how many Projects managers prefer not to have thorough requirements? Or don't want to deliver them. Any good IT Project Manager should be able to stand up to line by line focus on their stories.
​
In actual fact it's an aide to your program and reputation it's a safety net to ensure nothing is missed and risk to patient safety is minimised
2
Practical Application
As an Implementor of Technology in Health Care a high level overview of the
V Model will significantly help your planning and will remove around 30% of unfamiliar language.
​
Once explained it will change your opinion so you understand it as a safety net for your program and a case study for future reference and / or long term partnership.
We also hope that once explained it will turn your opinion to being a safety net for your program and a case study for future reference and / or long term partnership. Of the many formal signed documents (outside of commercials), you are only accountable to deliver and sign-off the Functional Specification, which is your line by line technical response to each line on the User Requirement Spec. This in itself is a significant document and can be challenging in an Agile world. In This course, we take the typical constructs of what you do today, In your various managed packages (Jira, Smart Sheets, Gannt Charts ...) and overlay the V-Model. Understanding it step by step, with a clear understanding of its purpose and RACI Matrix will align Client and Partner Program Leadership to an industry good practice. AKA GxP as we will explain on the day.