{'fraction_non_alphanumeric': 0.007860262008733625, 'fraction_numerical': 0.008733624454148471, 'mean_word_length': 5.262295081967213, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Methods for Preclinical Validation of Software as a Medical Device

: Software as a medical device is subject to dedicated regulatory requirements before it can be used on human beings. The certification process in Europe requires that sufficient data on clinical benefits are available before the device is CE marked. This position paper describes our proposal of a risk-based approach to technical and preclinical validation of software as medical devices. This approach ensures that all technical solutions for safety are implemented in the software and that all information for safe use is consistent before the software can be made available to patients. This approach is compliant to the main international standards ISO 13485 on quality systems and ISO 14971 on risk management and therefore ensures regulatory compliance as well as patient protection. This integrated approach allows the designers of the software to integrate regulatory and safety testing in the technical testing of the candidate release version of the device. This approach ensures patient safety and regulatory compliance at the same time as technical functionality.