Common use of System Logging Clause in Contracts

System Logging. The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

System Logging. The system must maintain an automated audit trail which can 20 22 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 23 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 24 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 25 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 26 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 27 three (3) years after occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 13 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 14 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 15 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 16 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 17 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 18 occurrence.

System Logging. The system must maintain an automated audit trail which can identify 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 21 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 22 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 23 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 24 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after 25 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 22 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 23 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 24 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 25 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 26 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after 27 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 24 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 25 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 26 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 27 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 28 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after 29 occurrence.

System Logging. The system must maintain an automated audit trail which can identify 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 21 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 22 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 23 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 24 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 25 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 22 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 23 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 24 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 25 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 26 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 27 years after occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 18 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 19 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 20 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 21 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 22 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 23 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 16 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 17 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 18 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 19 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 20 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after 21 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 22 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 23 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 24 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 25 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 26 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 27 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 17 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 18 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 19 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 20 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 21 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after 22 occurrence.

System Logging. The system must maintain an automated audit trail which that can 20 identify the user or system process which that initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

System Logging. The system must maintain an automated audit trail which can 20 13 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 14 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 15 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 16 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 17 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 18 three (3) years after occurrence.

System Logging. The system must maintain an automated audit trail which can 20 15 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 16 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 17 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 18 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 19 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 20 three (3) years after occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 11 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 12 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 13 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 14 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 16 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 17 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 18 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 19 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 20 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 21 three (3) years after occurrence.

System Logging. The system must maintain an automated audit trail which can 20 22 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 23 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 24 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 25 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored store d in a 24 26 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 27 three (3) years after occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 13 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 14 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 15 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 16 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 17 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after 18 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 12 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 13 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 14 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 15 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 16 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 17 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 15 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 16 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 17 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 18 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 19 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 20 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 22 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 23 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or 24 which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 25 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 26 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 27 three (3) years after occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 21 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 22 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 23 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 24 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 25 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 26 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 16 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 17 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 18 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after 19 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 4 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 5 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 6 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 7 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 18 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 19 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 20 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 21 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 22 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after 23 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 17 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 18 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 19 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 20 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 21 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 22 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 23 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 24 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 25 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 26 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 27 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 28 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 28 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 29 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 30 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 31 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 32 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 33 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 26 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 27 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 28 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 29 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 30 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 31 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 23 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 24 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 25 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 26 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 27 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after 28 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 14 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 15 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 16 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 17 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 18 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 19 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 9 of 14 EXHIBIT B CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after occurrence.

System Logging. The system must maintain an automated audit trail which can 20 14 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 15 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 16 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 17 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 18 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 19 three (3) years after occurrence.

System Logging. The system must maintain an automated audit trail which that can identify 20 identify the user or system process which that initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 21 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 22 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 23 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 24 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after 25 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 29 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 30 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 31 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 32 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 33 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 34 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 11 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 12 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 13 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 14 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 15 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 16 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 21 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 22 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 23 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 24 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 25 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 26 three (3) years after occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 16 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 17 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 18 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 19 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after 20 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 11 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 12 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 13 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after 14 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 8 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 9 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 10 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 11 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 12 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 13 three (3) years after occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 16 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 17 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 18 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 19 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 20 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 21 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 15 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 16 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 17 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 18 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 19 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after 20 occurrence.

System Logging. The system must maintain an automated audit trail which can 20 identify 9 the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or 10 CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such 11 PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must 12 be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database 13 logging functionality must be enabled. Audit trail data must be archived for at least 3 25 three (3) years after 14 occurrence.