Skip to content

Commit e04ce7e

Browse files
table
1 parent 8285b77 commit e04ce7e

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

articles/healthcare-apis/fhir/migration-strategies.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,8 @@ To migrate your data, follow these steps:
3333

3434
Compare the differences between Azure API for FHIR and Azure Health Data Services. Also review your architecture and assess if any changes need to be made.
3535

36-
|---**Capabilities** |---**Azure API for FHIR** |---**Azure Health Data Services** |
36+
|**Capabilities** |**Azure API for FHIR** |**Azure Health Data Services** |
37+
|---|---|---|
3738
| **Settings** | Supported: Local RBAC • SMART on FHIR Proxy | Planned deprecation - Local RBAC (9/6/23) - SMART on FHIR Proxy (9/21/26) | | |
3839
| **Data storage Volume** | More than 4 TB | Current support is 4 TB. Reach out to CSS team if you need more than 4 TB. | | |
3940
| **Data ingress** | Tools available in OSS | $import operation | | |
@@ -77,9 +78,9 @@ Identify data to migrate.
7778
Deploy a new Azure Health Data Services FHIR Service server.
7879
- First, deploy an Azure Health Data Services workspace.
7980

80-
- Then deploy an Azure Health Data Services FHIR Service server ([Deploy a FHIR service within Azure Health Data Services](fhir-portal-quickstart.md)
81+
- Then deploy an Azure Health Data Services FHIR Service server. More information: [Deploy a FHIR service within Azure Health Data Services](fhir-portal-quickstart.md)
8182

82-
- Configure your new Azure Health Data Services FHIR Service server. If you need to use the same configurations as you have in Azure API for FHIR for your new server, see the recommended list of what to check for in [migration tool documentation](https://microsoft.sharepoint.com/:w:/t/msh/Eb7WohSv_6JNlG1xAI8TyvoBbAPfhxnPzr4wv9py1InEww?e=QeSbo3&nav=eyJoIjoiMTUwODIzNzMifQ)). Configure the settings before you migrate.
83+
- Configure your new Azure Health Data Services FHIR Service server. If you need to use the same configurations as you have in Azure API for FHIR for your new server, see the recommended list of what to check for in the [migration tool documentation](https://microsoft.sharepoint.com/:w:/t/msh/Eb7WohSv_6JNlG1xAI8TyvoBbAPfhxnPzr4wv9py1InEww?e=QeSbo3&nav=eyJoIjoiMTUwODIzNzMifQ). Configure the settings before you migrate.
8384

8485
## Step 3: Migrate data
8586

0 commit comments

Comments
 (0)