{"component": "clause", "props": {"groups": [{"samples": [{"hash": "irIZ7ww41RZ", "uri": "/contracts/irIZ7ww41RZ#audit-capabilities", "label": "Contract Ma 042 25010171 for Software Maintenance and Database Hosting Services", "score": 36.0330216728, "published": true}, {"hash": "DSoiH1EYLr", "uri": "/contracts/DSoiH1EYLr#audit-capabilities", "label": "Lease Agreement", "score": 33.3916931152, "published": true}, {"hash": "5YtLXIBhSQ3", "uri": "/contracts/5YtLXIBhSQ3#audit-capabilities", "label": "Contract for Electronic Records Management System", "score": 31.1292762756, "published": true}], "size": 18, "snippet_links": [{"key": "changes-to", "type": "clause", "offset": [112, 122]}, {"key": "nature-of", "type": "clause", "offset": [189, 198]}, {"key": "audit-logs", "type": "definition", "offset": [440, 450]}, {"key": "access-to", "type": "definition", "offset": [494, 503]}, {"key": "authorized-users", "type": "definition", "offset": [528, 544]}, {"key": "the-application", "type": "clause", "offset": [548, 563]}, {"key": "query-tools", "type": "definition", "offset": [582, 593]}, {"key": "reports-to", "type": "clause", "offset": [598, 608]}, {"key": "record-retention", "type": "definition", "offset": [637, 653]}, {"key": "the-record", "type": "clause", "offset": [759, 769]}, {"key": "record-of", "type": "clause", "offset": [852, 861]}, {"key": "user-accounts", "type": "clause", "offset": [1109, 1122]}, {"key": "if-applicable", "type": "clause", "offset": [1241, 1254]}], "snippet": "Auditing and logging capabilities will permit HCA to identify, and possibly reverse, unauthorized or unintended changes to application. \u2022 Application must support the identification of the nature of each access and/or modification through the use of logging. \u2022 Application must employ audit capabilities to sufficiently track details that can establish accountability for each step or task taken in a clinical or operational process. \u2022 All audit logs must be protected from human alteration. \u2022 Access to logs must be limited to authorized users. \u2022 The application must employ basic query tools and reports to easily search logs. \u2022 OCHCA record retention policies must be followed. Currently OCHCA requires that this period be at least six years from the time the record was initiated. \u2022 Logging and auditing functionality must include the following: \u2666 Record of who did what to which object, when and on which system. \u2666 Successful/unsuccessful log-in and log-out of users. \u2666 Add, modify and delete actions on data/files/objects. \u2666 Read/view actions on data classified as restricted/confidential. \u2666 Changes to user accounts or privileges (creation, modification, deletion). \u2666 Switching to another users access or privileges after logging in (if applicable).", "hash": "0a155c6a5c1b8b68d625d0166d19ca4e", "id": 1}, {"samples": [{"hash": "aWZscKSZJ7q", "uri": "/contracts/aWZscKSZJ7q#audit-capabilities", "label": "Contract for Electronic Health Record System Maintenance and Support", "score": 31.1720581055, "published": true}, {"hash": "fHMMdzD07W9", "uri": "/contracts/fHMMdzD07W9#audit-capabilities", "label": "Contract for Electronic Health Record System Maintenance and Support", "score": 30.8668060303, "published": true}], "size": 4, "snippet_links": [{"key": "changes-to", "type": "clause", "offset": [114, 124]}, {"key": "county-of-orange", "type": "definition", "offset": [138, 154]}, {"key": "health-care-agency", "type": "definition", "offset": [155, 173]}, {"key": "nature-of", "type": "clause", "offset": [251, 260]}, {"key": "audit-logs", "type": "definition", "offset": [502, 512]}, {"key": "access-to", "type": "definition", "offset": [556, 565]}, {"key": "authorized-users", "type": "definition", "offset": [590, 606]}, {"key": "the-application", "type": "clause", "offset": [610, 625]}, {"key": "query-tools", "type": "definition", "offset": [644, 655]}, {"key": "reports-to", "type": "clause", "offset": [660, 670]}, {"key": "record-retention", "type": "definition", "offset": [699, 715]}, {"key": "the-record", "type": "clause", "offset": [821, 831]}, {"key": "record-of", "type": "clause", "offset": [914, 923]}, {"key": "user-accounts", "type": "clause", "offset": [1171, 1184]}, {"key": "if-applicable", "type": "clause", "offset": [1303, 1316]}], "snippet": "\u200c Auditing and logging capabilities will permit HCA to identify, and possibly reverse, unauthorized or unintended changes to application. County of Orange Health Care Agency Page 41 MA-042-17011367 \u2022 Application must support the identification of the nature of each access and/or modification through the use of logging. \u2022 Application must employ audit capabilities to sufficiently track details that can establish accountability for each step or task taken in a clinical or operational process. \u2022 All audit logs must be protected from human alteration. \u2022 Access to logs must be limited to authorized users. \u2022 The application must employ basic query tools and reports to easily search logs. \u2022 OCHCA record retention policies must be followed. Currently OCHCA requires that this period be at least six years from the time the record was initiated. \u2022 Logging and auditing functionality must include the following: \u2666 Record of who did what to which object, when and on which system. \u2666 Successful/unsuccessful log-in and log-out of users. \u2666 Add, modify and delete actions on data/files/objects. \u2666 Read/view actions on data classified as restricted/confidential. \u2666 Changes to user accounts or privileges (creation, modification, deletion). \u2666 Switching to another users access or privileges after logging in (if applicable).", "hash": "8147ce8245b791f0873e080a82b4e5bd", "id": 2}, {"samples": [{"hash": "grj94ph4z5D", "uri": "/contracts/grj94ph4z5D#audit-capabilities", "label": "Agreement for the Provision of Psychiatry Services", "score": 26.1399917603, "published": true}, {"hash": "znsb7BcSoT", "uri": "/contracts/znsb7BcSoT#audit-capabilities", "label": "Agreement for the Provision of Direct Digital Radiology Services", "score": 25.9995002747, "published": true}], "size": 3, "snippet_links": [{"key": "changes-to", "type": "clause", "offset": [121, 131]}, {"key": "nature-of", "type": "clause", "offset": [202, 211]}, {"key": "audit-logs", "type": "definition", "offset": [467, 477]}, {"key": "access-to", "type": "definition", "offset": [525, 534]}, {"key": "authorized-users", "type": "definition", "offset": [559, 575]}, {"key": "the-application", "type": "clause", "offset": [583, 598]}, {"key": "query-tools", "type": "definition", "offset": [617, 628]}, {"key": "reports-to", "type": "clause", "offset": [633, 643]}, {"key": "record-retention", "type": "definition", "offset": [676, 692]}, {"key": "the-record", "type": "clause", "offset": [801, 811]}, {"key": "record-of", "type": "clause", "offset": [902, 911]}, {"key": "user-accounts", "type": "clause", "offset": [1174, 1187]}, {"key": "if-applicable", "type": "clause", "offset": [1309, 1322]}], "snippet": "22 1. Auditing and logging capabilities will permit HCA to identify, and possibly reverse, 23 unauthorized or unintended changes to application.\n24 2. Application must support the identification of the nature of each access and/or modification 25 through the use of logging.\n26 3. Application must employ audit capabilities to sufficiently track details that can establish 27 accountability for each step or task taken in a clinical or operational process.\n28 4. All audit logs must be protected from human alteration.\n29 5. Access to logs must be limited to authorized users.\n30 6. The application must employ basic query tools and reports to easily search logs.\n31 7. OCHCA record retention policies must be followed. Currently OCHCA requires that this 32 period be at least six years from the time the record was initiated.\n33 8. Logging and auditing functionality must include the following:\n34 a. Record of who did what to which object, when and on which system.\n35 b. Successful/unsuccessful log-in and log-out of users.\n36 c. Add, modify and delete actions on data/files/objects.\n37 d. Read/view actions on data classified as restricted/confidential.\n1 e. Changes to user accounts or privileges (creation, modification, deletion).\n2 f. Switching to another users access or privileges after logging in (if applicable).", "hash": "a02f4c5e6d69359600b2347ed4efd4fe", "id": 3}, {"samples": [{"hash": "bx9JD8uBJCe", "uri": "/contracts/bx9JD8uBJCe#audit-capabilities", "label": "Environmental Health Data Management System Contract", "score": 30.2998542786, "published": true}, {"hash": "ha89MATzylk", "uri": "/contracts/ha89MATzylk#audit-capabilities", "label": "Environmental Health Data Management System Contract", "score": 23.6529769897, "published": true}], "size": 2, "snippet_links": [{"key": "changes-to", "type": "clause", "offset": [112, 122]}, {"key": "nature-of", "type": "clause", "offset": [189, 198]}, {"key": "audit-logs", "type": "definition", "offset": [430, 440]}, {"key": "access-to", "type": "definition", "offset": [484, 493]}, {"key": "authorized-users", "type": "definition", "offset": [518, 534]}, {"key": "the-application", "type": "clause", "offset": [538, 553]}, {"key": "query-tools", "type": "definition", "offset": [572, 583]}, {"key": "reports-to", "type": "clause", "offset": [588, 598]}, {"key": "record-of", "type": "clause", "offset": [686, 695]}, {"key": "user-accounts", "type": "clause", "offset": [820, 833]}], "snippet": "Auditing and logging capabilities will permit HCA to identify, and possibly reverse, unauthorized or unintended changes to application. \uf0b7 Application must support the identification of the nature of each access and/or modification through the use of logging. \uf0b7 Application must employ audit capabilities to sufficiently track details that can establish accountability for each step or task taken during operational process. \uf0b7 All audit logs must be protected from human alteration. \uf0b7 Access to logs must be limited to authorized users. \uf0b7 The application must employ basic query tools and reports to easily search logs. \uf0b7 Logging and auditing functionality must include the following: \uf0a8 Record of who did what to which object, when and on which system. \uf0a8 Successful/unsuccessful log-in and log-out of users. \uf0a8 Changes to user accounts or privileges (creation, modification, deletion).", "hash": "0406ead9e1156a798ad10094ceaeed02", "id": 4}, {"samples": [{"hash": "jAj4zMoapPP", "uri": "/contracts/jAj4zMoapPP#audit-capabilities", "label": "Agreement for Provision of Fiscal Intermediary Services", "score": 24.4174747467, "published": true}, {"hash": "geMnsteXTn", "uri": "/contracts/geMnsteXTn#audit-capabilities", "label": "Agreement for Provision of Health Exchange Outreach, Education and Assistance Services", "score": 23.1927871704, "published": true}], "size": 2, "snippet_links": [{"key": "changes-to-data", "type": "clause", "offset": [116, 131]}, {"key": "resulting-from", "type": "definition", "offset": [132, 146]}, {"key": "nature-of", "type": "clause", "offset": [224, 233]}, {"key": "operational-processes", "type": "definition", "offset": [458, 479]}, {"key": "audit-logs", "type": "definition", "offset": [491, 501]}, {"key": "comply-with", "type": "definition", "offset": [576, 587]}, {"key": "security-log-management", "type": "clause", "offset": [642, 665]}, {"key": "access-to", "type": "definition", "offset": [673, 682]}, {"key": "authorized-users", "type": "definition", "offset": [707, 723]}, {"key": "all-transactions", "type": "clause", "offset": [749, 765]}, {"key": "reporting-and-auditing", "type": "clause", "offset": [791, 813]}, {"key": "the-record", "type": "clause", "offset": [859, 869]}, {"key": "user-accounts", "type": "clause", "offset": [1226, 1239]}, {"key": "any-action", "type": "definition", "offset": [1368, 1378]}, {"key": "security-controls", "type": "clause", "offset": [1393, 1410]}, {"key": "date-of", "type": "clause", "offset": [1434, 1441]}, {"key": "the-system", "type": "definition", "offset": [1442, 1452]}, {"key": "software-errors", "type": "clause", "offset": [1492, 1507]}, {"key": "log-files", "type": "clause", "offset": [1531, 1540]}], "snippet": "5 a. Audit and logging capabilities will permit HCA to identify, and possibly reverse, 6 unauthorized or unintended changes to data resulting from error or misconduct.\n7 b. Application will support the identification of the nature of each access and/or 8 modification through the use of logging.\n9 c. Application will employ audit capabilities to sufficiently track details that can establish 10 accountability for each step or task taken in the clinical or operational processes.\n11 d. All audit logs will be protected from alteration.\n12 e. Audit/logging functionality will comply with NIST Special Publication 800-92, Guide 13 to Computer Security Log Management.\n14 f. Access to logs must be limited to authorized users.\n15 g. HCA requires that all transactions need to be available for reporting and auditing for a 16 least seven (7) years from the time the record was initiated.\n17 h. Auditing functionality must include the following:\n18 1) Record who did what to which object, when and on which system,\n19 2) Successful/unsuccessful log-in and log-out of users,\n20 3) Add, modify, print, and delete actions on data/files/objects,\n21 4) Read/view actions on data classified as restricted/confidential,\n22 5) Changes to user accounts or privileges (creation, modification, deletion),\n23 6) Switching to another users access or privileges after logging in,\n24 7) Any action to circumvent security controls,\n25 8) Changes of time/date of the system clock,\n26 9) Detection of hardware and software errors, and\n27 10) Changes to log files.", "hash": "edc85fcccaa43dac789cac87ca131fc7", "id": 5}, {"samples": [{"hash": "dRJA5EEgev8", "uri": "/contracts/dRJA5EEgev8#audit-capabilities", "label": "Contract for Inventory Management System", "score": 35.2261009216, "published": true}], "size": 1, "snippet_links": [{"key": "changes-to", "type": "clause", "offset": [112, 122]}, {"key": "for-cloud", "type": "clause", "offset": [201, 210]}, {"key": "hosted-solutions", "type": "clause", "offset": [211, 227]}, {"key": "malicious-code", "type": "clause", "offset": [315, 329]}, {"key": "the-application", "type": "clause", "offset": [433, 448]}], "snippet": "Auditing and logging capabilities will permit HCA to identify, and possibly reverse, unauthorized or unintended changes to application. Auditing and Logging functionality will include the following: \u2022 For cloud hosted solutions, vendors must utilize antivirus/antispyware software on servers and monitor to prevent malicious code which may lead to a compromise of OCHCA\u2019s data. \u2022 For local hosted solutions, vendors must ensure that the application appropriately supports the use of antivirus/antispyware software.", "hash": "2bf640927ad16c3c6ae48a4340c95093", "id": 6}, {"samples": [{"hash": "4vg6rQKp8kb", "uri": "/contracts/4vg6rQKp8kb#audit-capabilities", "label": "Agreement for Provision of Fiscal Intermediary Services", "score": 22.385263443, "published": true}], "size": 1, "snippet_links": [{"key": "changes-to-data", "type": "clause", "offset": [116, 131]}, {"key": "resulting-from", "type": "definition", "offset": [132, 146]}, {"key": "nature-of", "type": "clause", "offset": [224, 233]}, {"key": "operational-processes", "type": "definition", "offset": [458, 479]}, {"key": "audit-logs", "type": "definition", "offset": [491, 501]}], "snippet": "5 a. Audit and logging capabilities will permit HCA to identify, and possibly reverse, 6 unauthorized or unintended changes to data resulting from error or misconduct.\n7 b. Application will support the identification of the nature of each access and/or 8 modification through the use of logging.\n9 c. Application will employ audit capabilities to sufficiently track details that can establish 10 accountability for each step or task taken in the clinical or operational processes.\n11 d. All audit logs will be protected from alteration.", "hash": "d454c32c13b873296a97870e5d763e9e", "id": 7}, {"samples": [{"hash": "fHqhm0WLBzf", "uri": "/contracts/fHqhm0WLBzf#audit-capabilities", "label": "Telehealth and Digital Mental Health Support Services", "score": 32.8528022766, "published": true}], "size": 1, "snippet_links": [{"key": "changes-to", "type": "clause", "offset": [112, 122]}, {"key": "nature-of", "type": "clause", "offset": [189, 198]}, {"key": "audit-logs", "type": "definition", "offset": [440, 450]}, {"key": "access-to", "type": "definition", "offset": [494, 503]}, {"key": "authorized-users", "type": "definition", "offset": [528, 544]}, {"key": "the-application", "type": "clause", "offset": [548, 563]}, {"key": "query-tools", "type": "definition", "offset": [582, 593]}, {"key": "reports-to", "type": "clause", "offset": [598, 608]}, {"key": "record-retention", "type": "definition", "offset": [637, 653]}, {"key": "the-record", "type": "clause", "offset": [759, 769]}, {"key": "record-of", "type": "clause", "offset": [852, 861]}, {"key": "user-accounts", "type": "clause", "offset": [1109, 1122]}, {"key": "if-applicable", "type": "clause", "offset": [1241, 1254]}, {"key": "for-cloud", "type": "clause", "offset": [1257, 1266]}, {"key": "hosted-solutions", "type": "clause", "offset": [1267, 1283]}, {"key": "malicious-code", "type": "clause", "offset": [1371, 1385]}, {"key": "access-policy", "type": "clause", "offset": [1620, 1633]}], "snippet": "Auditing and logging capabilities will permit HCA to identify, and possibly reverse, unauthorized or unintended changes to application. \u2022 Application must support the identification of the nature of each access and/or modification through the use of logging. \u2022 Application must employ audit capabilities to sufficiently track details that can establish accountability for each step or task taken in a clinical or operational process. \u2022 All audit logs must be protected from human alteration. \u2022 Access to logs must be limited to authorized users. \u2022 The application must employ basic query tools and reports to easily search logs. \u2022 OCHCA record retention policies must be followed. Currently OCHCA requires that this period be at least six years from the time the record was initiated. \u2022 Logging and auditing functionality must include the following: \u2666 Record of who did what to which object, when and on which system. \u2666 Successful/unsuccessful log-in and log-out of users. \u2666 Add, modify and delete actions on data/files/objects. \u2666 Read/view actions on data classified as restricted/confidential. \u2666 Changes to user accounts or privileges (creation, modification, deletion). \u2666 Switching to another users access or privileges after logging in (if applicable). For cloud hosted solutions, vendors must utilize antivirus/antispyware software on servers and monitor to prevent malicious code which may lead to a compromise of OCHCA\u2019s data. \u2022 For local hosted solutions, vendors must ensure that the application appropriately supports the use of antivirus/antispyware software. \u2022 \u2022 Provider must conform to OCHCA Vendor Remote Access Policy.", "hash": "a06e737f038fe0f2c7563b5811a2c78d", "id": 8}, {"samples": [{"hash": "9yftDE8m9bs", "uri": "/contracts/9yftDE8m9bs#audit-capabilities", "label": "Contract for Eligibility Management System", "score": 33.4851341248, "published": true}], "size": 1, "snippet_links": [{"key": "changes-to", "type": "clause", "offset": [112, 122]}, {"key": "nature-of", "type": "clause", "offset": [189, 198]}, {"key": "audit-logs", "type": "definition", "offset": [440, 450]}, {"key": "access-to", "type": "definition", "offset": [494, 503]}, {"key": "authorized-users", "type": "definition", "offset": [528, 544]}, {"key": "the-application", "type": "clause", "offset": [548, 563]}, {"key": "query-tools", "type": "definition", "offset": [582, 593]}, {"key": "reports-to", "type": "clause", "offset": [598, 608]}, {"key": "docusign-envelope", "type": "definition", "offset": [629, 646]}, {"key": "record-retention", "type": "definition", "offset": [696, 712]}, {"key": "the-record", "type": "clause", "offset": [818, 828]}, {"key": "record-of", "type": "clause", "offset": [911, 920]}, {"key": "user-accounts", "type": "clause", "offset": [1168, 1181]}, {"key": "if-applicable", "type": "clause", "offset": [1300, 1313]}], "snippet": "Auditing and logging capabilities will permit HCA to identify, and possibly reverse, unauthorized or unintended changes to application. \u2022 Application must support the identification of the nature of each access and/or modification through the use of logging. \u2022 Application must employ audit capabilities to sufficiently track details that can establish accountability for each step or task taken in a clinical or operational process. \u2022 All audit logs must be protected from human alteration. \u2022 Access to logs must be limited to authorized users. \u2022 The application must employ basic query tools and reports to easily search logs. DocuSign Envelope ID: 32AC7F38-40B4-4FD7-9103-57D01A9AA5C7 \u2022 OCHCA record retention policies must be followed. Currently OCHCA requires that this period be at least six years from the time the record was initiated. \u2022 Logging and auditing functionality must include the following: \u2666 Record of who did what to which object, when and on which system. \u2666 Successful/unsuccessful log-in and log-out of users. \u2666 Add, modify and delete actions on data/files/objects. \u2666 Read/view actions on data classified as restricted/confidential. \u2666 Changes to user accounts or privileges (creation, modification, deletion). \u2666 Switching to another users access or privileges after logging in (if applicable).", "hash": "dfd070f59c87c54f0f27a0ac0a64dba3", "id": 9}, {"samples": [{"hash": "f1MimxixDgC", "uri": "/contracts/f1MimxixDgC#audit-capabilities", "label": "Professional Services", "score": 33.298992157, "published": true}], "size": 1, "snippet_links": [{"key": "protection-from-malicious-code", "type": "clause", "offset": [2, 32]}, {"key": "remote-support", "type": "clause", "offset": [154, 168]}], "snippet": "8 Protection from Malicious Code....................................................................................................................... 9 Remote Support Functionality .........................................................................................................................", "hash": "94aba56ec0917747a6c8d87bf09b5ccc", "id": 10}], "next_curs": "ClsSVWoVc35sYXdpbnNpZGVyY29udHJhY3RzcjcLEhZDbGF1c2VTbmlwcGV0R3JvdXBfdjU2IhthdWRpdC1jYXBhYmlsaXRpZXMjMDAwMDAwMGEMogECZW4YACAA", "clause": {"size": 36, "children": [], "parents": [["compliance-with-county-information-technology-policies-and-procedures", "Compliance with County Information Technology Policies and Procedures"], ["authority", "Authority"], ["contingency-of-funds", "Contingency of Funds"], ["application-functionality", "Application Functionality"], ["data-availability-management", "Data Availability Management"]], "title": "Audit Capabilities", "id": "audit-capabilities", "related": [["capabilities", "Capabilities", "Capabilities"], ["monitoring-services", "Monitoring Services", "Monitoring Services"], ["monitoring-activities", "Monitoring Activities", "Monitoring Activities"], ["operational-capability", "OPERATIONAL CAPABILITY", "OPERATIONAL CAPABILITY"], ["skills-and-abilities", "Skills and Abilities", "Skills and Abilities"]], "related_snippets": [], "updated": "2025-07-10T04:27:38+00:00"}, "json": true, "cursor": ""}}