Skip to content

Commit aeaf11c

Browse files
Merge pull request #277790 from EXPEkesheth/patch-170
Update fhir-service-diagnostic-logs.md
2 parents d03a751 + a0a4641 commit aeaf11c

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

articles/healthcare-apis/fhir/fhir-service-diagnostic-logs.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.author: kesheth
1313

1414
Access to diagnostic logs is essential for any healthcare service. Compliance with regulatory requirements like Health Insurance Portability and Accountability Act (HIPAA) is a must. In this article, you'll learn how to choose settings for diagnostic logs in the FHIR service within Azure Health Data Services. You'll also review some sample queries for these logs.
1515

16-
## Steps to enable diagnostic logs
16+
## Steps to enable logs
1717

1818
1. Select your FHIR service in the Azure portal.
1919

@@ -94,8 +94,7 @@ You can use these basic Log Analytics queries to explore your log data:
9494
| where ResultType == "Failed"`
9595

9696
## Conclusion
97-
98-
Having access to diagnostic logs is essential for monitoring a service and providing compliance reports. In this article, you learned how to enable these logs for the FHIR service.
97+
In this article, you learned how to enable these logs for the FHIR service. Having access to logs is essential for monitoring a service and providing compliance reports.
9998

10099

101100
## Next steps

0 commit comments

Comments
 (0)