Merge pull request #265095 from EXPEkesheth/patch-145

Update validation-against-profiles.md

Author: prmerger-automator[bot]

articles/healthcare-apis/azure-api-for-fhir/validation-against-profiles.md

@@ -108,14 +108,15 @@ If you'd like to specify a profile as a parameter, you can specify the canonical
 ## Validating a new resource
 
 If you'd like to validate a new resource that you're uploading to Azure API for FHIR, you can do a `POST` request:
+The server will always return an OperationOutcome as the result.
 
 `POST http://<your Azure API for FHIR base URL>/{Resource}/$validate`
 
 For example:
 
 `POST https://myAzureAPIforFHIR.azurehealthcareapis.com/Patient/$validate`
 
-This request will first validate the resource. New resource you're specifying in the request will be created after validation. The server will always return an OperationOutcome as the result.
+This request will validate the resource. On validation resources are not created in FHIR service, you will need to send a POST request without $validate to create resource.
 
 ## Validate on resource CREATE/ UPDATE using header.