Welcome to DHSC PIM

• Project Reports
• Sprint 6
• Sprint 5 (mid sprint)
• Sprint 5
• Sprint 4 (mid sprint)
• Sprint 4
• Sprint 3 (mid sprint)
• Sprint 3
• Sprint 2 (mid sprint)
• Sprint 2
• Sprint 1 (mid sprint)
• Sprint 1
• Sprint 0

Project Reports

Sprint 6

Weekly report

What we did last week

• Set up session with PAQ team
• Week 9 or 10 - Define what success looks like workshop
• Explore design approaches to data maintenance
• Plan manufacturer workshops for Sprint 5
• Add data and technical slides to the assessment show and tell slide deck
• Add context, constraint and beta plan slides to the assessment show and tell slide deck
• Set up session with DHSC supply resilience team
• Test PIM prototype with data consumers
• Add design slides to assessment show and tell slide deck

Things we’re still working on

• Add user research slides to the assessment show and tell slide deck
• Collate and produce alpha documentation
• Analyse data consumer survey responses [open until 28/06/2024]
• Set up session with NHSE outcome registries
• Tech call with assessment team (same week as show and tell) w/c 8th July [Waiting since 26th June]
• Set up session with NETIS (NHS SC)
• Get RC service map and data flows from MHRA [Waiting from 13/06/2024]
• Assess how we need to protect from or mitigate fraudulent or malicious activity
• Complete github documentation
• Create “Things to explore further in beta document”
• Investigate deduplicating products
• Week 11 or 12 (?) - Assessment team show and tell

Things to bear in mind

• This is the project’s last week - it will finish on Tuesday 16th July

Goals

• Get better data for analysis and prototyping Done

• Learn more about manufacturer incentives and constraints Done

• Document and outputs for Alpha In progress

These were the risks and issues identified in the project

• [Risk] Lack of Engagement from manufacturers in a maintenance process
• [Risk] Quality of Data - beyond our control
• [Risk] Consumer perception
• [Issue] Different people building different overlapping systems
• [Risk] Final ownership
• [Risk] NHS trust infrastructure to be able to consume data from PIM
• [Issue] What constitutes a medical device? How can we decide what is included and excluded from PIM
• [Risk] User availability
• [Risk] Access to data

Sprint 5 (mid sprint)

What we did last week

• Test PIM prototype with data consumers
• Set up and run session with PAQ team
• Plan and run manufacturer workshops for Sprint 5
• Add context, constraint and beta plan slides to the assessment show and tell slide deck
• Set up session with DHSC supply resilience team
• Add design slides to assessment show and tell slide deck
• Week 9 or 10 - Define what success looks like workshop
• Explore design approaches to data maintenance
• Add data and technical slides to the assessment show and tell slide deck

What we’re planning to do this week

• Complete github documentation
• Analyse data consumer survey responses
• Week 11 or 12 (?) - Assessment team show and tell
• Add user research slides to the assessment show and tell slide deck
• Tech call with assessment team (same week as show and tell) w/c 8th July [Waiting since 26th June]
• Assess how we need to protect from or mitigate fraudulent or malicious activity
• Get RC service map and data flows from MHRA
• Investigate deduplicating products
• Create “Things to explore further in beta document”
• Set up session with NETIS (NHS SC)
• Set up session with NHSE outcome registries
• Collate and produce alpha documentation

Goals

• Learn more about manufacturer incentives and constraints. In progress

• Document and outputs for Alpha In progress

These are our currently identified risks and issues

• [Risk]User availability
• [Risk]NHS trust infrastructure to be able to consume data from PIM
• [Risk] Lack of Engagement from manufacturers in a maintenance process
• [Risk] Consumer perception
• [Risk]Final ownership
• [Issue] Different people building different overlapping systems
• [Risk] Access to data
• [Issue] What constitutes a medical device? How can we decide what is included and excluded from PIM
• [Risk] Quality of Data - beyond our control

Sprint 5

Weekly report

What we did last week

• Appraise NHS Supply Chain
• Develop prototypes for data maintenance options
• Draft design for a cloud architecture
• Appraise EUDAMED
• Plan manufacturer workshop for Sprint 4
• Import full GMDN data (including hierarchies!)
• Identify best approach to API provision
• Plan manufacturer workshops for Sprint 5
• Identity - identify users to PIM, can we re-use existing MHRA structures to allow NHS and manufacturing users to log in?

What we’re planning to do this week

• Test PIM prototype with data consumers
• Create “Things to explore further in beta document”
• Assess how we need to protect from or mitigate fraudulent or malicious activity
• Explore design approaches to data maintenance
• Investigate deduplicating products
• Get RC service map and data flows from MHRA [Waiting from 13/06/2024]

Goals

• First prototype for data maintenance Done

• Get better data for analysis and prototyping In progress

• Learn more about manufacturer incentives and constraints In progress

• Document and outputs for Alpha In progress

These are are currently identified risks and issues

• [Risk]NHS trust infrastructure to be able to consume data from PIM
• [Risk]User availability
• [Risk] Quality of Data - beyond our control
• [Risk] Consumer perception
• [Risk] Access to data
• [Issue] Different people building different overlapping systems
• [Risk] Lack of Engagement from manufacturers in a maintenance process
• [Issue] What constitutes a medical device? How can we decide what is included and excluded from PIM
• [Risk]Final ownership

Sprint 4 (mid sprint)

What we did last week

• Research outputs to date
• Design iterations for next round of testing (data consumers)
• Add back-end for flag/request in prototype
• Design a data model for representing data provenance
• Decide approach for data engineering pipeline
• Content questions for UR
• Get list of GMDN categories that look like single attributes with multiple values
• Content iterations of prototype
• Import full GAMINE data (including hierarchies!)
• Understand GMDN license agreement
• Output - outlining manufacture incentives
• Sorting of search results in the prototype, especially by manufacturer
• Authz requirements for PIM users
• Graphic for data collection workflows to show manufacturers

What we’re planning to do this week

• Investigate de-duplicating products
• Explore design approaches to data maintenance
• Get RC service map and data flows from MHRA [Waiting from 13/06/2024]
• Identity - identify users to PIM, can we re-use existing MHRA structures to allow NHS and manufacturing users to log in?
• Import full GMDN data (including hierarchies!)
• Plan manufacturer workshop for Sprint 5
• Draft design for a cloud architecture
• Appraise NHS Supply Chain
• Develop prototypes for data maintenance options
• Assess how we need to protect from or mitigate fraudulent or malicious activity
• Plan manufacturer workshop for Sprint 4
• Identify best approach to API provision

Goals

• First prototype for data maintenance. In progress

• Get better data for analysis and prototyping In progress

These are our currently identified risks and issues

• [Risk] Access to data
• [Risk] Differing Visions of what’ we’re doing (Beta, proof of concept)
• [Issue] Different people building different overlapping systems
• [Risk] NHS trust infrastructure to be able to consume data from PIM
• [Issue] What constitutes a medical device? How can we decide what is included and excluded from PIM
• [Risk] Lack of Engagement from manufacturers in a maintenance process
• [Issue] Some comms teams won’t distribute calls for researchers in pre-election period.
• [Risk] Quality of Data - beyond our control
• [Risk] User availability
• [Risk] Final ownership
• [Risk] Consumer perception

Sprint 4

Weekly report

What we did last week

• Delivered a report giving advice on estimation strategies for PIM cash benefits
• Design a data model for representing data provenance
• CSV/XLS export and download - enables download of search results in CSV or EXCEL format
• We’ve obtained GMDN data and it has been loaded into a hierarchy - a demonstrator of this will be shown this week
• Output - outlining manufacture incentives
• Understand GMDN license agreement

What we’re planning to do this week

• Explore design approaches to data maintenance
• Plan manufacturer workshop for Sprint 4
• Import full GMDN data (including hierarchies!)
• Get RC service map and data flows from MHRA
• Sorting of search results in the prototype, especially by manufacturer
• Appraise NHS Supply Chain
• Decide approach for data engineering pipeline
• Research outputs to date
• Plan manufacturer workshop for Sprint 5
• Graphic for data collection workflows to show manufacturers
• Investigate de-duplication products
• Analyse data consumer survey responses
• Identify best approach to API provision
• Authz requirements for PIM users
• Identity - identify users to PIM, can we re-use existing MHRA structures to allow NHS and manufacturing users to log in?
• Design iterations for next round of testing (data consumers)

Goals

• First prototype for data maintenance. In progress

• Get better data for analysis and prototyping In progress

These are are currently identified risks and issues

• [Risk] Access to data

• [Risk] Differing Visions of what’ we’re doing (Beta, proof of concept)

• [Issue] Different people building different overlapping systems

• [Risk] NHS trust infrastructure to be able to consume data from PIM

• [Issue] What constitutes a medical device? How can we decide what is included and excluded from PIM

• [Risk] Lack of Engagement from manufacturers in a maintenance process

• [Issue] Some comms teams won’t distribute calls for researchers in pre-election period.

• [Risk] Quality of Data - beyond our control

• [Risk] User availability

• [Risk] Final ownership

• [Risk] Consumer perception

Sprint 3 (mid sprint)

What we did last week

• Add cleansing scripts and documentation to code repository
• Add quality analysis queries to code repository
• Assess record improvement of MHRA data using GUDID
• Draft and send out data consumers survey
• Ideation of data collection models
• Investigate quality issues with field validations in the MHRA dataset
• Investigate tech in Trust-hosted PIMS, such as Atrify, Elcom, GHX.
• Load MHRA DORS data into Design System-based prototype
• Map out possible to be user journey/service maps for data maintenance options
• Merge GUDID and MHRA data into a single SQLite db
• Recruit participants for Sprint 4 prototype testing
• Test coded prototype with data consumers [Round 3]

What we’re planning to do this week

• Consider guidance needs
• Content iterations of prototype
• CSV/XLS export
• Decide approach for data engineering pipeline
• Design a data model for representing data provenance
• Design iterations for next round of testing (data consumers)
• Explore design approaches to data maintenance
• Identify best approach to API provision
• Investigate deduplicating products
• Output - outlining manufacture incentives
• Plan manufacturer workshop for Sprint 4
• Research outputs to date
• Technical architecture recommendations
• Understand GMDN license agreement

Goals

• Get the dynamic search and view dynamic prototype ready Done

• Widen our participant pool Done

• Get better data for analysis and prototyping In progress

These are are currently identified risks and issues

• [Issue] Different people building different overlapping systems
• [Issue] Some comms teams won’t distribute calls for researchers in pre-election period.
• [Issue] What constitutes a medical device? How can we decide what is included and excluded from PIM
• [Risk] Access to data
• [Risk] Consumer perception
• [Risk] Differing Visions of what’ we’re doing (Beta, proof of concept)
• [Risk] Final ownership
• [Risk] Lack of Engagement from manufacturers in a maintenance process
• [Risk] NHS trust infrastructure to be able to consume data from PIM
• [Risk] User availability

Sprint 3

Weekly report

What we did last week

• Document attempts to match MHRA data directly with GUDID
• Improve search to include GMDN terms
• Tested the dynamic prototype with users
• Began drafting a to-be service map

What we’re planning to do this week

• Add cleansing scripts and documentation to code repository
• Add quality analysis queries to code repository
• Assess record improvement of MHRA data using GUDID
• Draft and send out data consumers survey
• Identify best approach to API provision
• Investigate field validations in the MHRA dataset
• Investigate external catalogue provider technologies
• Merge GUDID and MHRA data into a single SQLite db
• Plan manufacturer workshop for Sprint 4
• Test coded prototype with data consumers
• Research workshop with a medtech data platform project
• Mapping data maintenance user journeys
• Identifying design iterations to the dynamic prototype based on user feedback

Goals

These were the goals that we had last week:

• Get the dynamic search and view dynamic prototype ready Done

These are the goals that we have this week:

• Get better data for analysis and prototyping

In progress

• Understanding users responses to the coded prototype

In progress

• Widen our participant pool

In progress

These are are currently identified risks and issues

• [Issue] Different people building different overlapping systems
• [Issue] What constitutes a medical device? How can we decide what is included and excluded from PIM
• [Risk] Final ownership
• [Risk] Lack of Engagement from manufacturers in a maintenance process
• [Risk] NHS trust infrastructure to be able to consume data from PIM
• [Risk] Quality of Data - beyond our control
• [Risk] User availability

Screenshot of current PIM prototype

Sprint 2 (mid sprint)

What we did last week

• Add pagination to the dynamic prototype
• Build skeleton of dynamic prototype
• Define research plan for User Research in sprint 2
• Deploy dynamic prototype to external service
• Document and appraise the GS1 data fields
• Propose design ideas for maintenance of data
• Recommend iterations for prototypes based on research outputs
• Research - investigate what information trusts are asking manufacturers for
• Switch dynamic prototype to MHRA data
• Updates to data flows from user research so far

What we’re planning to do this week

• Content: Explore how the service could be maintained and improved in the future
• Document attempts to match MHRA data directly with GUDID
• Group analysis for round 2 - data providers
• Investigate quality issues with field validations in the MHRA dataset
• Investigate tech in Trust-hosted PIMS, such as Atrify, Elcom, GHX.
• Iterate prototypes - search

Goals

• Get the dynamic search and view dynamic prototype ready In progress
• Given current knowledge about ALPHA assumption - agree clarity on ROADMAP Done
• Widen our participant pool In progress

Things to bear in mind

• A four-week extension to the project has been agreed

These are are currently identified risks and issues

• [Issue] Different people building different overlapping systems
• [Risk] Differing opinions around what a PIM should be
• [Risk]Final ownership
• [Risk] Getting service assessment booked
• [Risk] Lack of Engagement from manufacturers in a maintenance process
• [Risk] NHS trust infrastructure to be able to consume data from PIM
• [Risk] PIM is an infrastructure that underpins multiple services - how do we frame what PIM is. What does “End-to-end” mean in this situation.
• [Risk] Quality of Data - beyond our control
• [Risk]User availability
• [Risk] What constitutes a medical device? How can we decide what is included and excluded from PIM

Sprint 2

What we did last week

• Add tools for downloading and ingesting public PARD data
• Compare the attributes required for each use case to what’s provided per data source
• Data flows workshop with MHRA
• Document the MHRA data schema
• Understand issues with PARD data governance

What we’re planning to do this week

• Acceptance criteria for design briefs
• Content: Explore how the service could be maintained and improved in the future
• Define research plan for User Research in sprint 2
• Document attempts to match MHRA data directly with GUDID
• Investigate quality issues with field validations in the MHRA dataset
• Investigate tech in Trust-hosted PIMS, such as Atrify, Elcom, GHX.
• Iterate prototypes - search
• Recommend iterations for prototypes based on research outputs
• Research - investigate what information trusts are asking manufacturers for

Goals

We have these goals this sprint (two-week period):

• Given current knowledge about ALPHA assumption - agree clarity on ROADMAP In progress
• Widen our participant pool In progress

Things to bear in mind

• We are currently discussing changes to the roadmap and possibly the lenght of the project in light of things that we’ve discovered through explorations of data and user research

These are are currently identified risks and issues

• /[Issue/] 13 fields may not be enough to provide value and / or solve the whole problem.
• /[Issue/] Different people building different overlapping systems
• /[Risk/]Final ownership
• /[Risk/] Getting service assessment booked
• /[Risk/] Lack of Engagement from manufacturers in a maintenance process
• /[Risk/] NHS trust infrastructure to be able to consume data from PIM
• /[Risk/] PIM is an infrastructure that underpins multiple services - how do we frame what PIM is. What does “End-to-end” mean is this situation.
• /[Risk/] Quality of Data - beyond our control
• /[Risk/]User availability
• /[Risk/] What constitutes a medical device? How can we decide what is included and excluded from PIM

Sprint 1 (mid sprint)

What we did last week

• Data flows workshop with MHRA
• Identify possible PIM prototyping options
• Investigate quality issues with GMDNs in the MHRA dataset
• Understand complexities with PARD data governance
• Group analysis session for round 1 data consumers
• “How might we” problem statements
• Interview with data provides

What we’re planning to do this week

• Identify possible PIM prototyping options
• Further user research group analysis sessions
• Content: Explore how the service could be maintained and improved in the future
• Document attempts to match MHRA data directly with GUDID
• Document the MHRA data schema
• Investigate quality issues with field validations in the MHRA dataset
• Investigate tech in Trust-hosted PIMS, such as Atrify, Elcom, GHX.
• MHRA/DHSC Tech appraisal
• Stakeholder interviews (data providers)
• Understand NHS eClass and ability to join with GMDN

Goals

We have one goal for this sprint (two-week period)

• Find out how people feel in NHS trusts about proposed view of 13 fields In progress

Things to bear in mind

• We are currently discussing a change to the programme of activities through the next two sprints with the service owner

These are are currently identified risks and issues

• [Issue] Different people building different overlapping systems
• [Risk] 13 fields may not be enough to provide value and / or solve the whole problem.
• [Risk] Engagement with manufacturers in a maintenance process
• [Risk] Final ownership
• [Risk] Getting service assessment booked
• [Risk] NHS trust infrastructure to be able to consume data from PIM
• [Risk] PIM is an infrastructure that underpins multiple services - how do we frame what PIM is. What does “End-to-end” mean is this situation.
• [Risk] User availability
• [Risk] What constitutes a medical device? How can we decide what is included and excluded from PIM

Sprint 1

What we did last week

• Agree ways of working
• Defining goals and KPIs
• Drafting user stories
• Exploring what we want to take into user testing
• Mapping the as-is service
• Mapping users and stakeholders
• Planning initial 2 user group workshops (data consumer)
• Completed first backlog refinement session
• Review participant list and address gaps for alpha
• Setting up service standard deck
• Conducted two data consumer workshops

What we’re planning to do this week

• Content: Explore how the service could be maintained and improved in the future
• Design prototypes for workshops
• Diagram possible data flows for collaborative maintenance
• Document attempts to match MHRA data directly with GUDID
• Document the MHRA data schema
• How might we… content statements
• Identify possible PIM prototyping options
• Investigate sign-in options (within MHRA/DHSC)
• MHRA/DHSC Tech appraisal
• Planning initial 2 user group workshops (data providers)
• Start diagrams for technical architecture

Goals

We have one goal for this sprint (two-week period)

• Find out how people feel in NHS trusts about proposed view of 13 fields In progress

Things to bear in mind

• We did a mini “Show and tell” showcasing our work last week on Wednesday 1st May
• Our next show and tell will be on Tuesday 14th May

These are are currently identified risks and issues

• [Issue] Engagement with manufacturers in a maintenance process
• [Risk] Final ownership
• [Issue] Different people building different overlapping systems
• [Issue] NHS trust infrastructure to be able to consume data from PIM
• [Risk] Getting service assessment booked
• [Risk] User availability

Sprint 0

What we did last week

• Questions for UR
• Understand medical device risk classes

What we’re planning to do this week

• Competitor content analysis
• Preparing for first backlog refinement session
• Access PARD/DORS source code via MHRA tech arch
• Mapping the as-is service
• Planning initial 2 user group workshops (data consumers / data providers)
• Get hold of a cut of the MHRA data
• Identify possible PIM prototyping options
• Mapping users and stakeholders
• Work with public PARD data and extract GMDN hierarchy
• Review participant list and address gaps for alpha
• Setting up service standard deck

Goals

These are our goals for this sprint

• Get access to Data In progress
• Understanding the existing service landscape In progress

Things to bear in mind

• This is our first week

These are are currently identified risks and issues

• [Issue] Different people building different overlapping systems
• [Risk] Getting service assessment booked
• [Risk] Access to data
• [Risk]User availability