Skip to content

Commit 63c4325

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into mrb_05_18_2023_ORA_updates
2 parents cafe230 + c601019 commit 63c4325

File tree

3 files changed

+23
-2
lines changed

3 files changed

+23
-2
lines changed

articles/azure-monitor/app/opentelemetry-configuration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -569,8 +569,8 @@ You might want to enable the OpenTelemetry Protocol (OTLP) Exporter alongside th
569569
var builder = WebApplication.CreateBuilder(args);
570570

571571
builder.Services.AddOpenTelemetry().UseAzureMonitor();
572-
builder.Services.ConfigureOpenTelemetryTracerProvider((sp, builder) => builder.AddOtlpExporter());
573-
builder.Services.ConfigureOpenTelemetryMeterProvider((sp, builder) => builder.AddOtlpExporter());
572+
builder.Services.AddOpenTelemetry().WithTracing(builder => builder.AddOtlpExporter());
573+
builder.Services.AddOpenTelemetry().WithMetrics(builder => builder.AddOtlpExporter());
574574

575575
var app = builder.Build();
576576

articles/healthcare-apis/azure-api-for-fhir/release-notes.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,13 @@ Azure API for FHIR provides a fully managed deployment of the Microsoft FHIR Ser
1818
> [!Note]
1919
> Azure Health Data services is the evolved version of Azure API for FHIR enabling customers to manage FHIR, DICOM, and MedTech services with integrations into other Azure Services. To learn about Azure Health Data Services [click here](https://azure.microsoft.com/products/health-data-services/).
2020
21+
## **May 2023**
22+
23+
**SMART on FHIR : Fixed clinical scope mapping for applications**
24+
25+
This bug fix addresses issue with clinical scope not interpreted correctly for backend applications.
26+
For more details, visit [#3250](https://github.com/microsoft/fhir-server/pull/3250)
27+
2128
## **April 2023**
2229

2330
**Fixed transient issues associated with loading custom search parameters**

articles/healthcare-apis/release-notes.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,20 @@ ms.custom: references_regions
1919
2020
Azure Health Data Services is a set of managed API services based on open standards and frameworks for the healthcare industry. They enable you to build scalable and secure healthcare solutions by bringing protected health information (PHI) datasets together and connecting them end-to-end with tools for machine learning, analytics, and AI. This document provides details about the features and enhancements made to Azure Health Data Services including the different service types (FHIR service, DICOM service, and MedTech service) that seamlessly work with one another.
2121

22+
## May 2023
23+
#### Azure Health Data Services
24+
25+
#### FHIR Service
26+
27+
**SMART on FHIR : Fixed clinical scope mapping for applications**
28+
29+
This bug fix addresses issue with clinical scope not interpreted correctly for backend applications.
30+
For more details, visit [#3250](https://github.com/microsoft/fhir-server/pull/3250)
31+
32+
**Addresses duplicate key error when passed in request parameters and body**
33+
34+
This bug fix handles the issue, when using the POST {resourcetype}/search endpoint to query FHIR resources, the server returns 415 Unsupported Media Type. This is due to repeating a query parameter in the URL query string and the request body. This fix considers all the query parameters from request and body as input. For more details, visit [#3232](https://github.com/microsoft/fhir-server/pull/3232)
35+
2236
## April 2023
2337
#### Azure Health Data Services
2438

0 commit comments

Comments
 (0)