fix GH issue #115082

Author: shellyhaverkamp

articles/healthcare-apis/logging.md

@@ -1,27 +1,25 @@
 ---
 title: Logging for Azure Health Data Services
-description: This article explains how logging works and how to enable logging for the Azure Health Data Services
+description: Learn to monitor Azure Health Data Services with AuditLogs for secure healthcare service trails and operational insights. Discover log types and uses.
 services: healthcare-apis
-author: chachachachami
+author: msjasteppe
 ms.service: healthcare-apis
 ms.topic: tutorial
-ms.date: 10/10/2022
-ms.author: chrupa
+ms.date: 06/12/2024
+ms.author: jasteppe
 ---
 
 # Logging for Azure Health Data Services
 
-The Azure platform provides three types of logs, activity logs, resource logs and Microsoft Entra logs. For more information, see [activity logs](../azure-monitor/essentials/platform-logs-overview.md). In this article, you’ll learn about how logging works for the Azure Health Data Services.
+In this article, you learn about how logging works for the Azure Health Data Services. Also, the Azure platform provides three types of logs, activity logs, resource logs, and Microsoft Entra logs. For more information, see [activity logs](../azure-monitor/essentials/platform-logs-overview.md). 
 
 ## AuditLogs
 While activity logs are available for each Azure resource from the Azure portal, Azure Health Data Services emits resource logs, which include two categories of logs, AuditLogs and DiagnosticLogs.
 
-- AuditLogs provide auditing trails for healthcare services. For example, a caller's IP address and resource URL are logged when a user or application accesses the FHIR service. Each service emits required properties and optionally implements additional properties.
-- DiagnosticLogs provides insight into the operation of the service, for example, log level (information, warning or error) and log message.
+- AuditLogs provide audit trails for healthcare services. For example, a caller's IP address and resource URL are logged when a user or application accesses the FHIR service. Each service emits required properties and optionally implements other properties.
+- DiagnosticLogs provides insight into the operation of the service, for example, log level (information, warning or error), and log message.
 
-At this time, Azure Health Data Services only supports AuditLogs.
-
-Below is one example of the AuditLog.
+Here's an example of the AuditLog:
 
 ```
 {
@@ -51,17 +49,10 @@ Below is one example of the AuditLog.
 
 ## Next steps
 
-In this article, you learned how to enable diagnostic logging for Azure Health Data Services. For more information about the supported metrics for Azure Health Data Services with Azure Monitor, see 
-
->[!div class="nextstepaction"]
->[Supported metrics with Azure Monitor](../azure-monitor/essentials/metrics-supported.md).
+[Supported metrics with Azure Monitor](../azure-monitor/essentials/metrics-supported.md).
 
-For more information about service logs and metrics for the DICOM service and MedTech service, see
+[Enable diagnostic logging in the DICOM service](./dicom/enable-diagnostic-logging.md)
 
->[!div class="nextstepaction"]
->[Enable diagnostic logging in the DICOM service](./dicom/enable-diagnostic-logging.md)
+[How to enable diagnostic settings for the MedTech service](./../healthcare-apis/iot/how-to-enable-diagnostic-settings.md)
 
->[!div class="nextstepaction"]
->[How to enable diagnostic settings for the MedTech service](./../healthcare-apis/iot/how-to-enable-diagnostic-settings.md)
 
-FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.

articles/healthcare-apis/toc.yml

@@ -54,7 +54,7 @@
       href: configure-private-link.md
     - name: Configure events
       href: ./events/events-deploy-portal.md
-    - name: Enable diagnostic logging
+    - name: Enable audit logging
       href: logging.md
     - name: Built-in policy definitions
       href: azure-health-data-services-policy-reference.md