[ ] Make it generalisable (in readme?) to non ML applications?
Suggestion for 4. Medical Device Regulations Classification Template:
[ ] Pre-populate the roles and responsibilities table if they're generic?
design-plan issues:
[ ] {device.mhra_classification} tag used but in device.yml the tag is {device.mhra_class}
risk.yml issues:
[ ] 'hazard_id' is used in the 'hazard-log.md' doc, but 'id' is used in risk.yml
device.yml issues:
[ ] 'BS62304_class' is used in medical-device-regulations-classification.md but in device.yml it is 'safety_class'. but safety_class is used in system-design-specification.md
requirements.yml issues:
[ ] in system-design-specification.md 'sys_des_spec' is expected but 'specification' is used in requirements.yml.
Create the list of the order of documents to fill in. this should follow the Design and development SOP to start with, with other QMS SOP following.
Order to fill out Templates