Merge pull request #103536 from CaitlinV39/master

Removed Cosmos reference from overview and updated supported features

Author: PRMerger8

articles/healthcare-apis/fhir-features-supported.md

@@ -36,8 +36,8 @@ Previous versions also currently supported include: `3.0.1`
 | create (conditional)           | Yes       | Yes       | Yes       |                                                     |
 | search                         | Partial   | Partial   | Partial   | See below                                           |
 | capabilities                   | Yes       | Yes       | Yes       |                                                     |
-| batch                          | No        | No        | No        |                                                     |
-| transaction                    | No        | No        | No        |                                                     |
+| batch                          | Yes       | Yes       | Yes       |                                                     |
+| transaction                    | No        | Yes       | No        |                                                     |
 | history                        | Yes       | Yes       | Yes       |                                                     |
 | paging                         | Partial   | Partial   | Partial   | `self` and `next` are supported                     |
 | intermediaries                 | No        | No        | No        |                                                     |
@@ -53,10 +53,10 @@ All search parameter types are supported. Chained parameters and reverse chainin
 | String                | Yes       | Yes       | Yes       |         |
 | Token                 | Yes       | Yes       | Yes       |         |
 | Reference             | Yes       | Yes       | Yes       |         |
-| Composite             | Yes       | Yes       | Yes       |        |
-| Quantity              | Yes       | Yes       | Yes       |Issue [#103](https://github.com/Microsoft/fhir-server/issues/103) |
+| Composite             | Yes       | Yes       | Yes       |         |
+| Quantity              | Yes       | Yes       | Yes       |         |
 | URI                   | Yes       | Yes       | Yes       |         |
-| Special               | No        | No        | No        |        
+| Special               | No        | No        | No        |         |
 
 
 | Modifiers             | Supported - PaaS | Supported - OSS (SQL) | Supported - OSS (Cosmos DB) | Comment |
@@ -71,6 +71,7 @@ All search parameter types are supported. Chained parameters and reverse chainin
 |`:not-in` (token)      | No        | No        | No        |         |
 |`:[type]` (reference)  | No        | No        | No        |         |
 |`:below` (uri)         | Yes       | Yes       | Yes       |         |
+|`:not`                 | No        | No        | No        |         |
 |`:above` (uri)         | No        | No        | No        | Issue [#158](https://github.com/Microsoft/fhir-server/issues/158) |
 
 | Common search parameter | Supported - PaaS | Supported - OSS (SQL) | Supported - OSS (Cosmos DB) | Comment |

articles/healthcare-apis/overview.md

@@ -22,7 +22,7 @@ Azure API for FHIR enables rapid exchange of data through Fast Healthcare Intero
 - Control your own data at scale with Role-Based Access Control (RBAC)
 - Audit log tracking for access, creation, modification, and reads within each data store
 
-Azure API for FHIR allows you to create and deploy a FHIR service in just minutes to leverage the elastic scale of the cloud.  You pay only for the throughput and storage you need. The Azure services that power Azure API for FHIR are designed for rapid performance no matter what size datasets you’re managing.  The data persistence layer in the Azure API for FHIR leverages Azure Cosmos DB, which guarantees latencies at the 99th percentile and guarantees high availability with multi-homing capabilities. 
+Azure API for FHIR allows you to create and deploy a FHIR service in just minutes to leverage the elastic scale of the cloud.  You pay only for the throughput and storage you need. The Azure services that power Azure API for FHIR are designed for rapid performance no matter what size datasets you’re managing.
 
 The FHIR API and compliant data store enable you to securely connect and interact with any system that utilizes FHIR APIs.  Microsoft takes on the operations, maintenance, updates, and compliance requirements in the PaaS offering, so you can free up your own operational and development resources.