Azure API for FHIR pricing

Easily create and deploy a FHIR service for health data solutions

“The Azure API for FHIR®” is a Platform-as-a-Service (PaaS) allowing organizations to upload, store, manage and analyze healthcare data in the Fast Healthcare Interoperability Resources (FHIR) format. Protected Heal Information (PHI) is protected and rights-managed, data can be analyzed and retrieved using Azure analysis tools, and servers are maintained and backed up by Microsoft. Azure allows practically limitless scalability and access to state-of-the-art machine learning tools.

Azure API for FHIR bills for service runtime that provides a RESTful API layer, Structured storage and Provisioned Throughput for the storage.

Service runtime is billed for every hour and covers the compute supporting the RESTful API layer that sits on top of the backend storage.

Structured Storage is billed for each GB used for your SSD-backed data and index.

Provisioned throughput is expressed in Request Units per second (RU/s), which can be used for various database operations (e.g., inserts, reads, replaces, upserts, deletes, queries, etc.). You can provision throughput and elastically scale in increments of 100 RU/s via Azure Portal.

Pricing Details

Price
Service Runtime $- per hour
Provisioned Throughput per 100 RU/s $- per hour
Structured Storage $-/month

FAQ

  • Customers should see charges for Azure API for FHIR to appear on their bill starting with the December 1, 2019 billing cycle.
    • Azure API for FHIR bills for the service runtime that provides RESTful API layer, Structured storage and Provisioned Throughput for the storage. The service runtime is billed for every hour and covers the compute. supporting the RESTful API layer that sits on top of the backend storage.
    • Structured Storage is billed for each GB used for SSD-backed data and index.
    • Provisioned throughput is expressed in Request Units per second (RU/s), which can be used for various database operations (e.g., inserts, reads, replaces, upserts, deletes, queries, etc.). Customers can provision throughput and elastically scale in increments of 100 RU/s via Azure Portal.
  • When the service was in Preview, the service consumption would show up as Cosmos DB charges in the billing statement. With the new billing model the service will show up as Azure API for FHIR in the statement. There is no change in charges for the storage usage of the service. However, Microsoft is now adding a cost for the service runtime that covers the compute part of the service.
  • Change in the billing means that usage of Azure API for FHIR will show up on the Azure billing statement as a separate service. This will give customers more transparent pricing on the service consumption. This will also give Microsoft the opportunity to explore different pricing tiers of the service in the future while adding more features for our customers.

Learn and build with $200 in credit, and keep going for free