
Diagnostic Innovation Platform in Primary Care: DIP-PC
About
In the journey of a diagnostic from idea to product, several gaps exist:
-
A lack of trustworthy evidence of a device/ test’s performance in real world settings
-
A gap in the communication between the producers, regulators and users of a technology/ device
-
A lack of understanding of core needs and contexts of primary care settings, especially in rural/remote areas, by engineers and technologists.

Scope of Interest to DIP-PC
Everything to do with diagnostics development, including:
-
Pre-conceptualization
-
Proof of Concept
-
Pilots
-
Clinical validation
-
Regulatory approvals
-
Clinical effectiveness
-
Real world implementation
-
Post marketing
We start with asking core questions of every diagnostic:
- Who is the intended primary beneficiary?
- In the healthcare journey of the intended beneficiary, where does the technology fit and what specific gap does it aim to bridge?
- Who is the intended primary user?
- What does the user need in order to get the diagnostic to work?
- Does the user have the ability to act on the results of the diagnostic or is this merely an additional step in their already existing, already overburdened workflows?
- Who is the payer?
- What other ecosystem changes or infrastructure are required for this technology to improve patient journeys and health outcomes?
- How does one prove that this technology has a positive impact on its intended beneficiaries?
- What are all the other confounders that could contribute to the results seen (either positive or negative) and how do you address them?
and many more..