Policy to require that changes in codes will follow the procedure shown in Figure 1 of FPHLM V5.0 document. 

All groups initiating changes in the model that requires changes in the computer code are required to submit detailed written proposals and requirement documentations including flowcharts to the computer science (CS) group and the program manager. The CS group will confirm sufficient documentation has been provided and request additional documentation as needed. A meeting will be held in which members of the initiating and related groups will meet members of the computer science group to discuss, clarify, provide feedback, and revise the requirement documentations as needed. A plan and time line to implement the changes in the code and test them will be established. Additional meetings will be held as required. If revisions are made the initiating team will provide the revised requirement documents to the CS group. Communications through e-mail, phone and or video conferencing will be maintained between the groups during the implementation process. Upon completion of the code revisions, the computer science team will inform the initiating group and the program manager that the codes are ready. The codes will be tested by the CS group and test results will be provided to all concerned groups. An  audit meeting will then be held by all related parties to review the codes and tests and verify the codes conform to the flowcharts and other requirement documents. If no errors are found, the changes can be approved by all parties for use. If errors are found they will either be corrected during the  audit or a plan will be established to remove the errors.   If needed a second  audit meeting will be held to review the testing, do a final check and approve use of the code. All documents related to this process will be held by the CS group.