Skip to content

Commit edcfc18

Browse files
Update app/breast-screening-reporting/2026/04/re-designing-image-reading-data-reporting-to-stress-test-the-reporting-roadmap/index.md
Co-authored-by: Frankie Roberto <frankie@frankieroberto.com>
1 parent b038a14 commit edcfc18

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • app/breast-screening-reporting/2026/04/re-designing-image-reading-data-reporting-to-stress-test-the-reporting-roadmap

app/breast-screening-reporting/2026/04/re-designing-image-reading-data-reporting-to-stress-test-the-reporting-roadmap/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ Below is an initial pass at modelling the data needed for image reading.
7878

7979
We drafted a data flow diagram to review feasibility with Information Governance and architects. Using synthetic data, we tested visualisation tools to recreate KPIs and complex QA charts while refining the data model.
8080

81-
![Comparison of data flow options across different platforms and tenants](./data-flow-drafting.png)
81+
![Comparison of data flow options across different platforms and tenants](data-flow-drafting.png)
8282

8383
We compared FDP’s visualisation tools with Azure-based options, including default dashboarding tools, open-source options and custom web builds. We also explored whether data processed in one platform could serve dashboards both within the image reader workflow and in a separate location for QA users who need to review multiple dashboards in one place.
8484

0 commit comments

Comments
 (0)