<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="stratmliso.xsl"?>
<StrategicPlan xmlns="urn:ISO:std:iso:17469:tech:xsd:stratml_core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:ISO:std:iso:17469:tech:xsd:stratml_core http://xml.govwebs.net/stratml/references/StrategicPlanISOVersion20140401.xsd"><Name>Proposed Content for an Algorithm Change Protocol (ACP)</Name><Description>An ACP is a description of the set of specific methods that a manufacturer has in place to achieve and
appropriately control the risks of the anticipated types of modifications delineated in the SPS. The ACP
provides a step-by-step delineation of the data and procedures to be followed so that the modifications
achieve their goals and the device remains safe and effective after the modification. The description
below is intended to highlight some components of an ACP, but is not intended to be an exhaustive list
of ACP components:</Description><OtherInformation/><StrategicPlanCore><Organization><Name>Food and Drug Administration</Name><Acronym>FDA</Acronym><Identifier>_85a3d7be-fbea-11df-a90e-29337a64ea2a</Identifier><Description/><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder></Organization><Vision><Description/><Identifier>_08a72f26-5a1f-11e9-9ee9-02f17d73fa26</Identifier></Vision><Mission><Description>To define the content of an Algorithm Change Protocol (ACP) for AI/ML-based software as a medical device</Description><Identifier>_08a7305c-5a1f-11e9-9ee9-02f17d73fa26</Identifier></Mission><Value><Name/><Description/></Value><Goal><Name>Data Management</Name><Description>Issue plans addressing how data will be collected, added to existing data sets, and used.</Description><Identifier>_08a73124-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>Data management plan addressing how data will be collected, added to existing data sets, and used:  This data management plan may include a quality assurance (QA) plan for determining which new data are appropriate for inclusion as part of an expanded training data set; an approach to the reference standard determination; a data augmentation strategy that allows for additional training and independent test data to be added; and an auditing and sequestration strategy to monitor, document test dataset independence, and control access to both the training and test datasets as additional data are being included and any revised algorithm is being retrained and tested.</OtherInformation><Objective><Name>Quality Assurance</Name><Description>Include a quality assurance (QA) plan for determining which new data are appropriate for inclusion as part of an expanded training data set</Description><Identifier>_08a731d8-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>1.1</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Reference Standards</Name><Description>Include an approach to the reference standard determination</Description><Identifier>_08a7328c-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>1.2</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Data Augmentation</Name><Description>Include a data augmentation strategy that allows for additional training and independent test data to be added</Description><Identifier>_08a73340-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>1.3</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Auditing &amp; Sequestration</Name><Description>Include an auditing and sequestration strategy to monitor, document test dataset independence, and control access to both the training and test datasets as additional data are being included and any revised algorithm is being retrained and tested.</Description><Identifier>_08a733ea-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>1.4</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Re-Training &amp; Optimization</Name><Description>Define protocols for re-training / optimizing medical device algorithms.</Description><Identifier>_08a734a8-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>Protocols for re-training / optimizing the medical device algorithm: These protocols may include a retraining strategy that describes the objective of the retraining; the algorithm components that may be modified as a result of the learning process; and any criteria that must be met during the re-training process to trigger a more comprehensive performance evaluation using the test dataset.</OtherInformation><Objective><Name>Objectives</Name><Description>Describe the objective of the retraining</Description><Identifier>_08a7355c-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>2.1</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Algorithm Components</Name><Description>Describe the algorithm components that may be modified as a result of the learning process</Description><Identifier>_08a73610-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>2.2</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Criteria</Name><Description>Describe any criteria that must be met during the re-training process to trigger a more comprehensive performance evaluation using the test dataset.</Description><Identifier>_08a736ce-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>2.3</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Performance Evaluation</Name><Description>Evaluate the performance of the algorithms.</Description><Identifier>_08a7378c-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>3</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>Performance evaluation protocols: These protocols may include a description of the intervals of when a new algorithm may be trained and evaluated to consider updating the medical device algorithm; the delineation of appropriate metrics and analysis procedures; statistical analysis plans; appropriate measures to minimize information leakage about the test data set if part of it is re-used in multiple evaluations; performance targets that the revised algorithm must achieve; and protocols for testing, which may be applicable for that device and type of change, for example, for testing “with clinicians in the loop,” as appropriate. </OtherInformation><Objective><Name>Intervals</Name><Description>Describe the intervals of when a new algorithm may be trained and evaluated to consider updating the medical device algorithm</Description><Identifier>_08a7384a-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>3.1</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Metrics &amp; Analysis</Name><Description>Delineate appropriate metrics and analysis procedures</Description><Identifier>_08a73926-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>3.2</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Statistical Analyses</Name><Description>Document statistical analysis plans</Description><Identifier>_08a739f8-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>3.3</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Information Leakage</Name><Description>Institute appropriate measures to minimize information leakage about the test data set if part of it is re-used in multiple evaluations</Description><Identifier>_08a73ab6-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>3.4</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Performance Targets</Name><Description>Specify performance targets that the revised algorithm must achieve</Description><Identifier>_08a73b88-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>3.5</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Testing</Name><Description>Define protocols for testing, which may be applicable for that device and type of change, for example, for testing “with clinicians in the loop,” as appropriate. </Description><Identifier>_08a73c5a-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>3.6</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Updates</Name><Description>Describe how updated medical device algorithms will be tested, distributed, and communicated when released.</Description><Identifier>_08a73d22-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>4</SequenceIndicator><Stakeholder StakeholderTypeType="Generic_Group"><Name/><Description/></Stakeholder><OtherInformation>Update procedures that describe how updated medical device algorithms will be tested, distributed, and communicated when released: These update procedures may include a description of the update plan including expected frequency of updates and whether the updates will be global (all devices use the same version of the algorithm) or local (multiple versions of the algorithm targeted for specific subpopulations are distributed); version tracking and control; obsolescence planning; requirements for host software/hardware requirements; any plans for ‘beta’ release of the updated medical device algorithm concurrent with the previous version; and communication procedures that describe how users will be notified of updates and any information that will be conveyed to users about the update.</OtherInformation><Objective><Name>Plan</Name><Description>Include a description of the update plan</Description><Identifier>_08a73e4e-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>4.1</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Versioning</Name><Description>Address version tracking and control</Description><Identifier>_08a73f20-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>4.2</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Obsolescence</Name><Description>Plan for obsolescence</Description><Identifier>_08a73fe8-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>4.3</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Software &amp; Hardware</Name><Description>Specify requirements for host software/hardware requirements</Description><Identifier>_08a740f6-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>4.4</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Beta Releases</Name><Description>Document any plans for ‘beta’ release of the updated medical device algorithm concurrent with the previous version</Description><Identifier>_08a741d2-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>4.5</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Communications</Name><Description>Document communication procedures that describe how users will be notified of updates and any information that will be conveyed to users about the update.</Description><Identifier>_08a7429a-5a1f-11e9-9ee9-02f17d73fa26</Identifier><SequenceIndicator>4.6</SequenceIndicator><Stakeholder StakeholderTypeType=""><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate>2019-04-02</StartDate><PublicationDate>2019-04-08</PublicationDate><Source>https://www.regulations.gov/document?D=FDA-2019-N-1185-0001</Source><Submitter><GivenName>Owen</GivenName><Surname>Ambur</Surname><PhoneNumber/><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></StrategicPlan>