A gateway for health data and protected health information (PHI) in the cloud
Azure Health Data Services is a Platform-as-a-Service (PaaS) allowing organisations to upload, store, manage and analyse healthcare data in the open standards of Fast Healthcare Interoperability Resources (FHIR) & Digital Imaging and Communications in Medicine (DICOM). Azure Health Data Services workspaces can be configured with MedTech service, which is used to ingest data from IoT/IoMT devices for monitoring, storage, analysis, and reporting of vital health information. Protected Health Information (PHI) is protected and rights-managed, data can be analysed 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.
Explore pricing options
Apply filters to customize pricing options to your needs.
Prices are estimates only and are not intended as actual price quotes. Actual pricing may vary depending on the type of agreement entered with Microsoft, date of purchase, and the currency exchange rate. Prices are calculated based on US dollars and converted using London closing spot rates that are captured in the two business days prior to the last business day of the previous month end. If the two business days prior to the end of the month autumn on a bank holiday in major markets, the rate setting day is generally the day immediately preceding the two business days. This rate applies to all transactions during the forthcoming month. Sign in to the Azure pricing calculator to see pricing based on your current programme/offer with Microsoft. Contact an Azure sales specialist for more information on pricing or to request a price quote. See frequently asked questions about Azure pricing.
US government entities are eligible to purchase Azure Government services from a licensing solution provider with no upfront financial commitment or directly through a pay-as-you-go online subscription.
Important—The price in R$ is merely a reference; this is an international transaction and the final price is subject to exchange rates and the inclusion of IOF taxes. An eNF will not be issued.
US government entities are eligible to purchase Azure Government services from a licensing solution provider with no upfront financial commitment or directly through a pay-as-you-go online subscription.
Important—The price in R$ is merely a reference; this is an international transaction and the final price is subject to exchange rates and the inclusion of IOF taxes. An eNF will not be issued.
Azure Health Data Services
Azure Health Data Services is the evolved version of Azure API for FHIR and offers additional technology and services. With Azure Health Data Services you pay only for what you use. With the new pricing model, you are granted a monthly allotment that enables you to try the product for free.
| Storage (per GB/month) | Up to 1 GB | Over 1 GB |
| Structured Storage | $- | $- |
| BLOB Storage | $- | $- |
| API Requests (per 1,00,000 requests) | Up to 50K | Over 50K |
| API Requests | $- | $- |
| Transformation Operations (per MB) | Up to 50 MB | Over 50 MB |
| Unstructured De-identification | $- | $- |
| Transformation Operations (per GB) | Up to 0.5 GB | Over 0.5 GB |
| FHIR Transformations | $- | $- |
| Structured De-identification | $- | $- |
| Transcode DICOM | $- | $- |
| Export Operations (per GB) | Up to 1 GB | Over 1 GB |
| Export batch | $- | $- |
| Eventing (per 10,00,000 events) | Up to 100K | Over 100K |
| Events | $- | $- |
Storage
Charges for storage include the volume of data ingested into the service and its indexes.
Use of the DICOM service will incur charges for both Structured storage and BLOB storage. DICOM images incur BLOB storage charges based on the size of the object ingested and stored while its metadata will incur structured storage charges.
API Requests
Operations with status codes 500 or higher and 429 will not incur a charge. Initial mode import does not incur charge.
The FHIR standard defines the ability to execute a “bundle”, which is a grouping of multiple related resources, each with its own operation. A bundle may be posted as a Batch or Transaction. When using Batch, operations that are successfully executed from the bundle will incur a charge. When using Transactions, all bundle operations succeed or fail as a whole, and only successful transactions will incur a charge.
The DICOM service enables multi-part requests where multiple DICOM instances can be stored or retrieved with a single request. Multi-part requests will incur a charge per DICOM instance stored or retrieved.
Transformation Operations
When using the MedTech service, converting data in device proprietary formats to FHIR will incur FHIR Transformations charges. In addition, posting those FHIR resources to the FHIR service will incur API request charges.
Azure API for FHIR
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.
Features that allow you to convert and de-identify data will be made generally available. Charges for the use of these features are shown in the table below. These capabilities will be free to use while in it’s preview state until the end of the year.
In addition, the use of the export capability will now incur charges, shown in the same table below, as well.
De-identified export will incur separate charges, for de-identification and export.
| Unit | Price |
|---|---|
| Service Runtime | $- per hour |
| Provisioned Throughput per 100 RU/s | $- per hour |
| Structured Storage | $-/GB/month |
| Transformations | $-/GB |
| De-Identification | $-/GB |
| Export | $-/GB |
Auto scaling Pricing
By default, Azure API for FHIR is set to manual scaling. When Auto Scaling is enabled, there is a 50% increase in the cost of the provisioned throughput. While the billing rate remains unchanged, the throughput units are adjusted with a multiplier of 1.5. There is no change to the cost of service runtime or of structured storage. Auto-scaling can be enabled through a customer support request. Find out more here.
Disaster Recovery Pricing
When disaster recovery is enabled, an instance of Azure API for FHIR is replicated in an Azure paired region, thereby doubling the total cost of the service. Disaster Recovery can be enabled through a customer support request. Find out more here.
Azure pricing and purchasing options
Connect with us directly
Get a walkthrough of Azure pricing. Understand pricing for your cloud solution, learn about cost optimisation and request a custom proposal.
Talk to a sales specialistSee ways to purchase
Purchase Azure services through the Azure website, a Microsoft representative or an Azure partner.
Explore your optionsAdditional resources
Azure Healthcare APIs
Learn more about Azure Healthcare APIs features and capabilities.
Pricing calculator
Estimate your expected monthly costs for using any combination of Azure products.
SLA
Review the Service Level Agreement for Azure Healthcare APIs.
Documentation
Review technical tutorials, videos and more Azure Healthcare APIs resources.
Frequently asked questions
-
For the duration of public preview, Azure Healthcare APIs is available free of charge.
-
- 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.
-
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.
-
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.
Talk to a sales specialist for a walk-through of Azure pricing. Understand pricing for your cloud solution.
Get free cloud services and a $200 credit to explore Azure for 30 days.