-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #39 from Marvell-Consulting/PIM20240617
Pim20240617
- Loading branch information
Showing
2 changed files
with
70 additions
and
0 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,70 @@ | ||
| --- | ||
| title: Sprint 4 | ||
| date: 2024-06-17 | ||
| description: Sprint report for DHSC PIM Sprint 4 | ||
| --- | ||
|
|
||
| Weekly report - elderberries | ||
| ============================ | ||
|
|
||
|  | ||
|
|
||
| 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 | ||
| - GMDN hierarchy | ||
| - Output - outlining manufacture incentives | ||
| - CSV/XLSX/ODS download | ||
| - 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 | ||
| - 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 deduplicating products | ||
| - Analyse data consumer survey responses | ||
| - Identify best approach to API provision | ||
| - Authz requirements for PIM users | ||
| - Identity | ||
| - Design iterations for next round of testing (data consumers) | ||
|
|
||
| Goals | ||
| ----- | ||
|
|
||
| - First prototype for data maintenance. | ||
| <span class="badge bg-info">_**In progress**_</span> | ||
|
|
||
| - Get better data for analysis and prototyping | ||
| <span class="badge bg-info">_**In progress**_</span> | ||
|
|
||
| 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 |