Skip to content

Commit 2052525

Browse files
authored
Update fhir-service-autoscale.md
1 parent 889a360 commit 2052525

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/healthcare-apis/fhir/fhir-service-autoscale.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,9 @@ ms.author: kesheth
1111

1212
# Autoscaling
1313

14-
Azure Health Data Services provides a managed service for persisting FHIR-compliant healthcare data and interacting with it securely through the API service endpoint. The autoscaling feature for FHIR service is designed to provide optimized service scalability automatically to meet customer demands when they perform data transactions in consistent or various workloads at any time.
14+
Azure Health Data Services provides a managed service for persisting FHIR-compliant healthcare data and interacting with it securely through the API service endpoint.
1515

16-
Autoscaling is a capability to dynamically scale your FHIR service based on the load reported. The FHIR service in Azure Health Data Services provides the built-in autoscale capability and the process is automated. The capability provides elasticity and enables provisioning of additional instances for your FHIR service on demand.
16+
Autoscaling is a capability to dynamically scale your FHIR service based on the load reported. The FHIR service in Azure Health Data Services provides the built-in autoscale capability and the process is automated. The capability provides elasticity and enables provisioning of additional instances for customers FHIR service on demand.
1717

1818
The autoscaling feature adjusts computing resources automatically to optimize service scalability. There is no action required from customers.
1919

@@ -28,7 +28,7 @@ Autoscaling policies defined for FHIR service consists of two parts:
2828
* Scaling Trigger
2929

3030
Scaling Trigger describes when scaling of the service will be performed. Conditions that are defined in the trigger are checked periodically to determine if a service should be scaled or not. All triggers that are currently supported are Average CPU, Max Worker Thread, Average LogWrite, Average data IO.
31-
31+
3232
* Scaling mechanism
3333

3434
Scaling Mechanism describes how scaling will be performed when it is triggered. Mechanism is only applied when the conditions from the trigger are met.
@@ -48,7 +48,7 @@ Autoscaling policies defined for FHIR service consists of two parts:
4848

4949
### What is the cost to enable autoscaling for FHIR service?
5050

51-
The autoscaling feature incurs no extra costs to customers based on the new API billing model.
51+
The autoscaling feature incurs no extra costs to customers.
5252

5353
## Next steps
5454

0 commit comments

Comments
 (0)