Testing software-only device on hardware - What are the hardware parameters?

S

SSchoepel

Involved In Discussions
Hello, I'm now working for a company that is developing a software-only medical device. I've only worked in places where there was also hardware/equipment. Our testing was always on a "production or production-equivalent system."

I realize we need to test on operating systems that we will support and that those will be on specific hardware. How do I say this without saying that we will have production-equivalent systems?

Can I say something about platform-equivalent systems and define what I mean by platform? Like Microsoft Windows 8 laptop, MacBook Pro running iOS 10.1.3, etc. Can I say that we have a minimum configuration on which it runs and test to that? "Minimum configuration-equivalent"?

Just wondering how others state and map to the test systems when it's software-only.

Thank you,
S Schoepel
 
S

SSchoepel

Involved In Discussions
This is what I came up with for our test plan and the hardware compatibility requirements will list the minimum system requirements for the platforms/computers/devices on which we will design the product to run:

[FONT=&quot]The testing is run on all supported hardware configurations (see the hardware compatibility requirements for the configurations) unless exceptions are indicated in this section.[/FONT]

I think it's sufficient.

Yes? No?

S. Schoepel
 
michellemmm

michellemmm

Quest For Quality
SSchoepel said:
This is what I came up with for our test plan and the hardware compatibility requirements will list the minimum system requirements for the platforms/computers/devices on which we will design the product to run:

[FONT=&quot]The testing is run on all supported hardware configurations (see the hardware compatibility requirements for the configurations) unless exceptions are indicated in this section.[/FONT]

I think it's sufficient.

Yes? No?

S. Schoepel
Click to expand...

I am a little confused. Are you trying to test hardware or are you testing integration of hardware and software?
 
S

SSchoepel

Involved In Discussions
I am trying to test a software-only product on platforms/configurations that we will stated as being tested on/compatible with the software-only product. I've come from a "big iron" medical device company where we always tested on "production-equivalent" systems because we shipped a physical product. Not sure how to state properly what kind of test systems we are testing on for a software-only product.

Regards,
S. Schoepel
 
Y

yodon

Leader
Super Moderator
The first question I'd ask would be what happens if the system fails on a system on which it wasn't tested? What are the risks of not testing?

The second question I'd ask is what the spectrum of configurations looks like. If you can say that 90% of the population is anticipated to run on a set of configurations and there's no substantial risk for running on the others, maybe you test the 90%.

I know that systems deployed over browsers have the capability to know what browser (and maybe hardware configuration?) is being used so you could possibly prohibit use on untested configurations (or provide a pop-up saying, effectively, use at your own risk).
 
C

c.mitch

Quite Involved in Discussions
Hi Sschoepel,
I went through the same questions as yours when submitting PACS standalone software to the FDA. And I was also challenged by the developers team about FDA requirements.
I stumbled upon your posts and I felt less alone :)
About your questions on level of concern, I had the same problem. Minor a few years ago, FDA now "prefers" moderate for this kind of software.
About hardware/software platform compatibility, I went through different solutions: from freezing the configuration to having only minimum system requirements like those you mentioned.
Minimum requirements in the user/install instructions + tests on this configuration passed the exam of the FDA.
Now if you have web technology in your software, things get more complex. You'd better be more specific on the browsers you support and if your PACS viewer runs on smartphones/tablets (and I don't talk about cybersecurity and human factors engineering!)
A good source of information is to have a look at 510k summaries of your competitors. Eg: GE centricity universal viewer or zero footprint viewer. They're really intructive.

Anyway, Yodon's risk based approach is probably the best method to define rationale to stick to a configuration or to leave it open with minimum requirements.
 
You must log in or register to reply here.
Thread starter Similar threads Forum Replies Date
S Sample performance testing for a software-only medical device 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 1
R Medical Device Software - Final Field Testing Best Practices IEC 62304 - Medical Device Software Life Cycle Processes 5
A Beta Testing FDA Regulated Medical Device Software vs. Nonconforming product? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 3
T Aircraft GAPP Software Testing Compliance Question AS9100, IAQG, NADCAP and Aerospace related Standards and Requirements 1
X Looking for 17025 auditor to perform internal audit on IT software testing laboratory ISO 17025 related Discussions 3
R Validation of Software used in Verification Testing ISO 13485:2016 - Medical Device Quality Management Systems 2
I Software (SaMD) mobile application verification testing: objective evidence Medical Information Technology, Medical Software and Health Informatics 6
gramps What do you think about automated QA testing For software app industry? Misc. Quality Assurance and Business Systems Related Topics 5
L Traditional 510(K) - Software - Clinical testing? 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 1
S Script of R software to conduct Nested GRR for Destructive Testing Gage R&R (GR&R) and MSA (Measurement Systems Analysis) 0
S Certified Manager of Software Testing (CMST) Certification Exam Career and Occupation Discussions 4
C Software for trending and reporting particulate testing Quality Assurance and Compliance Software Tools and Solutions 2
S IEC 60601-1 Cl. 14 - Report changes in Software after Testing to Test Lab? IEC 60601 - Medical Electrical Equipment Safety Standards Series 4
S Verify Software System Testing: Verify that results meet the Pass/Fail Criteria IEC 62304 - Medical Device Software Life Cycle Processes 1
Z Floppy Disk Software Control - Floppy Disk with Software for Testing Document Control Systems, Procedures, Forms and Templates 4
G Green Belt Project in Software Testing Six Sigma 1
K Tips on answering the questions for Certified Manager for Software Testing (CMST)? Career and Occupation Discussions 15
B Software Beta Testing - Sample test plan or procedure wanted Other Medical Device and Orthopedic Related Topics 5
R Innovations and Best Practice in Software Testing Software Quality Assurance 5
S Automated regression testing software Software Quality Assurance 4
U What are the Advantages and Benefits of Independent Testing of Software? Software Quality Assurance 5
D Validating software in materials testing - Integrated system of individual components General Measurement Device and Calibration Topics 3
Marc Software Quality Assurance is More than Testing and IEEE Standard 12207 Software Quality Assurance 0
C 7.6 for a Software Company - Calibrating Unit Testing ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 7
A Calibration Software Validation - Are there any Testing Tools available? Calibration and Metrology Software and Hardware 8
Marc Calibration of Software used for Testing Purposes General Measurement Device and Calibration Topics 2
Marc Calibration of Software used for testing purposes General Measurement Device and Calibration Topics 5
Marc ISO/IEC 12119 - Software packages - Quality requirements and testing Software Quality Assurance 3
I Labeling requirements for Type Testing China Medical Device Regulations 1
T Human Factors and Usability Testing in the US - smaller sample size than the required 15 users Human Factors and Ergonomics in Engineering 6
H Regarding 47 CFR 15c testing CE Marking (Conformité Européene) / CB Scheme 3
O ESD Testing IEC 60601 IEC 60601 - Medical Electrical Equipment Safety Standards Series 7
Stoic Which medical device companies are using Recombinant Factor C (rFC) instead of Limulus Amebocyte Lysate (LAL) for endotoxin testing? Sustainability, Green Initiatives and Ecology 0
S Testing & Validation Phase Design and Development of Products and Processes 1
I Design Verification Testing on Non-Validated Equipment ISO 13485:2016 - Medical Device Quality Management Systems 2
R Quality Agreements with external testing laboratories now mandatory? EU Medical Device Regulations 16
A New biocompatibility testing? US Medical Device Regulations 1
S Guidance on Factory Acceptance Testing for injection moulds please Qualification and Validation (including 21 CFR Part 11) 2
C Biocompatability Testing - Electric Breast Pumps , Silicone Component EU Medical Device Regulations 3
L Proficiency Testing Statistical Analysis ISO 17025 related Discussions 0
T Changes to product IFU & Summative Testing IEC 62366 - Medical Device Usability Engineering 1
A Chemotherapy Resistance Testing for EU EU Medical Device Regulations 1
N FDA mechanical bench testing Manufacturing and Related Processes 5
E Microbial Barrier Testing for Medical Devices Qualification and Validation (including 21 CFR Part 11) 2
A Safety testing of Medical devices ISO 13485:2016 - Medical Device Quality Management Systems 2
C When should I take endotoxin testing？ EU Medical Device Regulations 3
A Safety testing for Medical devices to be sold in India ISO 13485:2016 - Medical Device Quality Management Systems 0
M Test Lab Recommends ANSI C63.27 Wireless Coexistence Testing IEC 60601 - Medical Electrical Equipment Safety Standards Series 8
P Biocompatibility testing ISO-10993 for FDA submission Other Medical Device Related Standards 7
R Tips on transitioning out of testing lab Career and Occupation Discussions 0

Similar threads

Top Bottom