Merge pull request #227903 from EXPEkesheth/patch-47

Update store-profiles-in-fhir.md

Author: prmerger-automator[bot]

articles/healthcare-apis/fhir/store-profiles-in-fhir.md

@@ -67,13 +67,13 @@ Profiles are also specified by various Implementation Guides (IGs). Some common
 
 ### Storing profiles
 
-To store profiles in Azure API for FHIR, you can `PUT` the `StructureDefinition` with the profile content in the body of the request. A standard `PUT` or a conditional update are both good methods to store profiles on the FHIR service. Use the conditional update if you are unsure which to use.
+To store profiles in FHIR service, you can `PUT` the `StructureDefinition` with the profile content in the body of the request. A standard `PUT` or a conditional update are both good methods to store profiles on the FHIR service. Use the conditional update if you are unsure which to use.
 
-Standard `PUT`: `PUT http://<your Azure API for FHIR base URL>/StructureDefinition/profile-id`
+Standard `PUT`: `PUT http://<your FHIR service base URL>/StructureDefinition/profile-id`
 
 **or**
 
-Conditional update: `PUT http://<your Azure API for FHIR base URL>/StructureDefinition?url=http://sample-profile-url`
+Conditional update: `PUT http://<your FHIR service base URL>/StructureDefinition?url=http://sample-profile-url`
 
 ```
 { 
@@ -87,7 +87,7 @@ Conditional update: `PUT http://<your Azure API for FHIR base URL>/StructureDefi
 For example, if you'd like to store the `us-core-allergyintolerance` profile, you'd use the following rest command with the US Core allergy intolerance profile in the body. We've included a snippet of this profile for the example.
 
 ```rest
-PUT https://myAzureAPIforFHIR.azurehealthcareapis.com/StructureDefinition?url=http://hl7.org/fhir/us/core/StructureDefinition/us-core-allergyintolerance
+PUT https://<your FHIR service base URL>/StructureDefinition?url=http://hl7.org/fhir/us/core/StructureDefinition/us-core-allergyintolerance
 ```
 
 ```json
@@ -125,7 +125,7 @@ You can access your existing custom profiles using a `GET` request, ``GET http:/
 
 For example, if you want to view US Core Goal resource profile:
 
-`GET https://myworkspace-myfhirserver.fhir.azurehealthcareapis.com/StructureDefinition?url=http://hl7.org/fhir/us/core/StructureDefinition/us-core-goal`
+`GET https://<your FHIR service base URL>/StructureDefinition?url=http://hl7.org/fhir/us/core/StructureDefinition/us-core-goal`
 
 This will return the `StructureDefinition` resource for US Core Goal profile, that will start like this:
 
@@ -203,6 +203,13 @@ You'll be returned with a `CapabilityStatement` that includes the following info
         "http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient"
     ],
 ```
+
+### Bindings in Profiles
+A terminology service is a set of functions that can perform operations on medical “terminologies,” such as validating codes, translating codes, expanding value sets, etc.  The FHIR service doesn't support terminology service. Information for supported operations ($), resource types and interactions can be found in the service's CapabilityStatement. Resource types ValueSet, StructureDefinition and CodeSystem are supported with basic CRUD operations and Search (as defined in the CapabilityStatement) as well as being leveraged by the system for use in $validate. 
+
+ValueSets can contain a complex set of rules and external references. Today, the service will only consider the pre-expanded inline codes. Customers need to upload supported ValueSets to the FHIR server prior to utilizing the $validate operation. The ValueSet resources must be uploaded to the FHIR server, using PUT or conditional update as mentioned under Storing Profiles section above. 
+
+
 ## Next steps
 
 In this article, you've learned about FHIR profiles. Next, you'll learn how you can use $validate to ensure that resources conform to these profiles.