Skip to content

Commit 14b80f2

Browse files
Merge pull request #238117 from EXPEkesheth/patch-64
Update using-curl.md
2 parents 1b58cce + 30b9d03 commit 14b80f2

File tree

3 files changed

+9
-3
lines changed

3 files changed

+9
-3
lines changed

articles/healthcare-apis/fhir/use-postman.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,8 @@ Create a new `POST` request:
8585
- **client_secret**: `{{clientsecret}}`
8686
- **resource**: `{{fhirurl}}`
8787

88-
Note : In the scenarios where FHIR service audience parameter is not mapped to FHIR service endpoint url, the resource parameter value should be mapped to Audience value under FHIR Service Authentication blade.
88+
> [!NOTE]
89+
> In the scenarios where the FHIR service audience parameter is not mapped to the FHIR service endpoint url. The resource parameter value should be mapped to Audience value under FHIR Service Authentication blade.
8990
9091
3. Select the **Test** tab and enter in the text section: `pm.environment.set("bearerToken", pm.response.json().access_token);` To make the value available to the collection, use the pm.collectionVariables.set method. For more information on the set method and its scope level, see [Using variables in scripts](https://learning.postman.com/docs/sending-requests/variables/#defining-variables-in-scripts).
9192
4. Select **Save** to save the settings.

articles/healthcare-apis/fhir/using-curl.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,6 +77,8 @@ token=$(az account get-access-token --resource=$dicomtokenurl --query accessToke
7777
```
7878

7979
---
80+
> [!NOTE]
81+
> In the scenarios where the FHIR service audience parameter is not mapped to the FHIR service endpoint url. The resource parameter value should be mapped to Audience value under FHIR Service Authentication blade.
8082
8183
## Access data in the FHIR service
8284

@@ -125,4 +127,4 @@ To learn about how to access Azure Health Data Services data using REST Client e
125127
>[!div class="nextstepaction"]
126128
>[Access Azure Health Data Services using REST Client](using-rest-client.md)
127129
128-
FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
130+
FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.

articles/healthcare-apis/fhir/using-rest-client.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,9 @@ grant_type=client_credentials
6868

6969
[ ![Get access token](media/rest-config.png) ](media/rest-config.png#lightbox)
7070

71+
> [!NOTE]
72+
> In the scenarios where the FHIR service audience parameter is not mapped to the FHIR service endpoint url. The resource parameter value should be mapped to Audience value under FHIR Service Authentication blade.
73+
7174
## `GET` FHIR Patient data
7275

7376
You can now get a list of patients or a specific patient with the `GET` request. The line with `Authorization` is the header info for the `GET` request. You can also send `PUT` or `POST` requests to create/update FHIR resources.
@@ -107,4 +110,4 @@ To learn about how to validate FHIR resources against profiles in Azure Health D
107110
>[!div class="nextstepaction"]
108111
>[Validate FHIR resources against profiles in Azure Health Data Services](validation-against-profiles.md)
109112
110-
FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
113+
FHIR® is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.

0 commit comments

Comments
 (0)