Azure Health Data Services

azure NoSQL databaseazure-health-data-services

Managed FHIR, DICOM and de-identification APIs for storing and exchanging health data in a workspace.

Provider: azure
Kind: NoSQL database
Category: Data
Official docs: https://learn.microsoft.com/en-us/azure/healthcare-apis/healthcare-apis-overview

Properties · 2 set by this component

property	type	values	required	kind default	this component
auditLogging · component property	boolean	—	no	true	inherited
backupEnabled	boolean	—	no	false	inherited
backupRetentionDays	integer	—	no	—	inherited
bucketing · advanced	boolean	—	no	false	inherited
conflictResolution	enum	none \| last-writer-wins \| vector-clock \| app-merge	no	—	inherited
consistency	enum	eventual \| tunable \| strong	no	eventual	inherited
customerManagedKeys · component property	boolean	—	no	false	inherited
encryptionAtRest	boolean	—	no	false	inherited
instances	integer	—	no	—	inherited
managed	boolean	—	no	false	▸ true
model	enum	key-value \| wide-column \| document	yes	—	▸ document
partitionKey	string	—	no	—	inherited
privateLink · component property	boolean	—	no	false	inherited
quorumReads · advanced	integer	—	no	—	inherited
quorumWrites · advanced	integer	—	no	—	inherited
rbacEntraId · component property	boolean	—	no	true	inherited
replication	enum	single-region \| multi-region-single-leader \| multi-region-multi-leader \| leaderless	no	single-region	inherited
replicationFactor	integer	—	no	—	inherited
service · component property	enum	fhir \| dicom \| de-identification	no	fhir	inherited
tombstoneTtlDays · advanced	integer	—	no	—	inherited

Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

Multi-leader store without a conflict policywarning

multi-leader-store-without-conflict-policy

Multi-leader replication accepts concurrent writes in several regions. With no conflict resolution policy declared, divergent replicas are reconciled by accident rather than by design.

— all of these hold:
— the node's `replication` is "multi-region-multi-leader"
— any of these hold:
— the node's `conflictResolution` has no value
— the node's `conflictResolution` is "none"

Read-heavy datastore without a cachewarning

read-heavy-path-without-cache

The design states a read-heavy workload and application servers read this datastore directly, yet the design has no cache anywhere. Every read pays a database round trip.

— all of these hold:
— the design requirement `traffic.readWriteRatio` is a number greater than 10
— the node has at least one synchronous incoming edge from an app-server
— this does not hold:
— the design contains a node of kind cache

Use it in a design

nodes:
  - { id: "health-data-services", component: "azure-health-data-services" }

Other NoSQL database products · 46

ApsaraDB for HBasealibaba-apsaradb-hbasealibabacloudnosql-database ApsaraDB for MongoDBalibaba-apsaradb-mongodbalibabacloudnosql-database Lindormalibaba-lindormalibabacloudnosql-database Tablestorealibaba-tablestorealibabacloudnosql-database Amazon CloudFront KeyValueStoreaws-cloudfront-keyvaluestoreawsnosql-database Amazon Cognito Syncaws-cognito-syncawsnosql-database Amazon DocumentDBaws-documentdbawsnosql-database AWS HealthLakeaws-healthlakeawsnosql-database Amazon Keyspaces (for Apache Cassandra)aws-keyspacesawsnosql-database Amazon DynamoDBdynamodbawsnosql-database Azure Cosmos DBazure-cosmos-dbazurenosql-database Azure DocumentDBazure-documentdbazurenosql-database Azure Managed Instance for Apache Cassandraazure-managed-cassandraazurenosql-database Azure Table Storageazure-table-storageazurenosql-database Workers KVcloudflare-workers-kvcloudflarenosql-database Apache Accumuloaccumulonosql-database Aerospike Databaseaerospikenosql-database Apache Cassandracassandranosql-database Couchbasecouchbasenosql-database Apache CouchDBcouchdbnosql-database DataStax Enterprisedatastax-enterprisenosql-database FoundationDBfoundationdbnosql-database Apache HBasehbasenosql-database MarkLogic Servermarklogicnosql-database MongoDBmongodbnosql-database MongoDB Atlasmongodb-atlasnosql-database Generic NoSQL databasenosql-databasenosql-database NoSQL storenosql-storenosql-database OrientDBorientdbnosql-database RavenDBravendbnosql-database RethinkDBrethinkdbnosql-database Riak KVriaknosql-database ScyllaDBscylladbnosql-database TiKVtikvnosql-database YDBydbnosql-database Google Cloud Bigtablebigtablegcpnosql-database Google Cloud Firestorefirestoregcpnosql-database Cloud Healthcare APIgoogle-cloud-healthcare-apigcpnosql-database Firebase Realtime Databasegoogle-firebase-realtime-databasegcpnosql-database Firestore in Datastore modegoogle-firestore-datastore-modegcpnosql-database

and 6 more → NoSQL database page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Azure Health Data Services: workspace of managed PaaS health-data APIs (FHIR, DICOM,
3# de-identification). FHIR data is stored as documents in a database unique to each service instance,
4# reachable only through the API, with Microsoft Entra RBAC. Facts from "What is Azure Health Data
5# Services?" and "What is the FHIR service in Azure Health Data Services?".
6schemaVersion: "1"
7type: "component"
8id: "azure-health-data-services"
9kind: "nosql-database"
10provider: "azure"
11docs: "https://learn.microsoft.com/en-us/azure/healthcare-apis/healthcare-apis-overview"
12defaults:
13  managed: true
14  model: "document"
15properties:
16  service:
17    type: "enum"
18    values: ["fhir", "dicom", "de-identification"]
19    default: "fhir"
20  rbacEntraId:
21    type: "boolean"
22    default: true
23  privateLink:
24    type: "boolean"
25    default: false
26  customerManagedKeys:
27    type: "boolean"
28    default: false
29  auditLogging:
30    type: "boolean"
31    default: true

The same page as markdown, for an agent: /catalogue/components/azure-health-data-services.md