Development of an equipment and calibration verification framework

1. Martin Green, Richard Clements Development of an equipment and calibration verification framework

2. Background • Reliant on users and process to assure quality • Taking a reliable overview not possible

3. Requirements • Record QA test results • Easily accessible by multiple concurrent users • Overview of failing QA • Show trends in parameters • Allow tests to be performed efficiently • Temporally aware

4. Development Methodology V-model Independent Acceptance Plan Requirements Acceptance Testing System Testing Plan System Requirements System Verifications Integration Testing Plan Design Integration Testing Test Driven Development Coding Unit Testing

5. Development Methodology Incremental Picture: Incremental Model/RahulT/Creative Commons

6. System Requirements Can we hard code an application to perform the tests we require? • There are hundreds of different tests • The tests we have are regularly changing • Tests are for multiple sub disciplines A framework was required to allow domain experts to configure the QA program Accessibility requirements fulfilled by a web application

7. System Requirements - Stacks Server Side Client Side

8. System Requirements - Django Request HTTP Get/Post Response HTML, JSON, JS, CSS Controller URL dispatcher Model Object Relational Mapper View Process requests Template

9. Design - Data Model Configuration Routine Equipment Type Equipment Classification Equipment Instance Calibration Type Calibration Instance Calibration Verification Requirement Calibration Verification Instance Calibration Verification Type Form Type Form Instance

10. Design - Calibrations 10MV Linac Output Calibration Type Calibration Instance • Unique ID Prefix • 10XEOUTPUT • Named Variables and Units • Output - cGy/MU • Named Equipment • Linac – 10MV Linac • Unique ID • 10XEOUTPUT5 • Variables • Output: 1.0 cGy/MU • Equipment • Linac: M10-5 Rowan • Conditions • 100cm SSD, 10cm x 10cm field • at Dmax depth • References • Reference to controlled document • AuthorisationFrom 2010-12-11 (JBloggs) Examples shown in grey

11. Design - Calibration Verifications Water Farmer Output Check Calibration Verification Type • Input Values • Temperature - °C, Pressure – mbar, Readings - nC • Input Calibrations (calibrations contain variables) • Energy, Felec,Fion,NDw • Calculations • FTP = (Temperature + 273) * 1013.25 / (293 * Pressure) • Rmean (nC) = mean(R1, R2, R3) • Output (cGy/MU) = Rmean* FTP * NDw.Value * Felec.Value * Fion.Value / Energy.PDD5 • Pass Function • abs(calibration.Output-Output) / calibration.Output < 0.03 • Validations • 15 < Temperature < 30 - Temperature outside expected range • 0.02 > abs(calibration.Output-Output)/calibration.Output - Please check your setup Examples shown in grey

12. Design - Forms Water Farmer Output Check Form Type

13. Design - Forms Water Farmer Output Check Form Instance

14. Design - Forms Water Farmer Output Check Form Instance

15. Design - Graphs Linac Output Checks

16. Design - Dashboard - Overview

17. Design - Dashboard – Drilling Down

18. Situation so far • Implemented checks: • Linac, brachytherapy and orthovoltage output checks • Radiographer daily checks • Automated server disk space checks • Saves time during morning machine checks • In use for 4 years • 30,000 forms entered • 200,000 checks recorded

19. Further Work • Allow verifications to depend upon other verifications: • Eg. Definitive calibrations rely upon: • Beam profile checks and • Farmer chamber consistency checks • Train more Domain Experts • Implement remaining QA checks • Automate System verification

20. Further Work – Graphing Seth M. Powsner and Edward R. Tufte, "Graphical Summary of Patient Status", The Lancet 344 (August 6, 1994), 386-389