You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/healthcare-apis/fhir/migration-strategies.md
+7-8Lines changed: 7 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,8 +32,7 @@ To migrate your data, follow these steps:
32
32
## Step 1: Assess readiness
33
33
34
34
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.
35
-
36
-
|**Capabilities**|**Azure API for FHIR**|**Azure Health Data Services**|||
35
+
|---**Capabilities**|---**Azure API for FHIR**|---**Azure Health Data Services**|||
|**Settings**| Supported: Local RBAC • SMART on FHIR Proxy | Planned deprecation - Local RBAC (9/6/23) - SMART on FHIR Proxy (9/21/26) |||
39
38
|**Data storage Volume**| More than 4 TB | Current support is 4 TB. Reach out to CSS team if you need more than 4 TB. |||
@@ -48,9 +47,9 @@ Compare the differences between Azure API for FHIR and Azure Health Data Service
48
47
49
48
-**Sync agent is being deprecated**. If you're using sync agent to connect to Dataverse, see [Overview of data integration toolkit](/dynamics365/industry/healthcare/data-integration-toolkit-overview?toc=%2Findustry%2Fhealthcare%2Ftoc.json&bc=%2Findustry%2Fbreadcrumb%2Ftoc.json)
50
49
51
-
-**FHIR Proxy is being deprecated**. If you're using FHIR Proxy for events, refer to the built-in [eventing](./../events/events-overview.md/) feature. Alternatives can be customized and built using the [Azure Health Data Services toolkit](https://github.com/microsoft/azure-health-data-services-toolkit).
50
+
-**FHIR Proxy is being deprecated**. If you're using FHIR Proxy for events, refer to the built-in [eventing](../events//events-overview.md/) feature. Alternatives can be customized and built using the [Azure Health Data Services toolkit](https://github.com/microsoft/azure-health-data-services-toolkit).
52
51
53
-
-**SMART on FHIR proxy is being deprecated**. You need to use the new SMART on FHIR capability. More information: [SMART on FHIR](/healthcare-apis/fhir/smart-on-fhir)
52
+
-**SMART on FHIR proxy is being deprecated**. You need to use the new SMART on FHIR capability. More information: [SMART on FHIR](smart-on-fhir.md)
54
53
55
54
-**Azure Health Data Services FHIR Service does not support local RBAC and custom authority**. The token issuer authority needs to be the authentication endpoint for the tenant that the FHIR Service is running in.
56
55
@@ -64,12 +63,12 @@ First, create a migration plan. We recommend the migration patterns described in
| Lift and shift | The simplest pattern. Ideal if your data pipelines can afford longer downtime. | Choose the option that works best for your organization: Configure a workflow to [\$export](/healthcare-apis/azure-api-for-fhir/export-data.md) your data on Azure API for FHIR, and then [\$import](/healthcare-apis/fhir/configure-import-data.md) into Azure Health Data Services FHIR Service. The [GitHub repo](https://github.com/Azure/apiforfhir-migration-tool/blob/main/v0/V0_README.md) provides tips on running these commands, and a script to help automate creating the \$import payload. Or, create your own tool to migrate the data using \$export and \$import. |
66
+
| Lift and shift | The simplest pattern. Ideal if your data pipelines can afford longer downtime. | Choose the option that works best for your organization: Configure a workflow to [\$export](../azure-api-for-fhir/export-data.md) your data on Azure API for FHIR, and then [\$import](configure-import-data.md) into Azure Health Data Services FHIR Service. The [GitHub repo](https://github.com/Azure/apiforfhir-migration-tool/blob/main/v0/V0_README.md) provides tips on running these commands, and a script to help automate creating the \$import payload. Or, create your own tool to migrate the data using \$export and \$import. |
68
67
| Incremental copy | Continuous version of lift and shift, with less downtime. Ideal for large amounts of data that take longer to copy, or if you want to continue running Azure API for FHIR during the migration. | Choose the option that works best for your organization. We created an [OSS migration tool](https://github.com/Azure/apiforfhir-migration-tool/blob/main/v0/V0_README.md) to help with this migration pattern. Or, create your own tool to migrate the data incrementally.
69
68
70
69
### OSS migration tool considerations
71
70
72
-
If you decide to use the OSS migration tool, review and understand the migration tool’s [capabilities and limitations](https://github.com/Azure/apiforfhir-migration-tool/incremental-copy-docs/Appendix.md).
71
+
If you decide to use the OSS migration tool, review and understand the migration tool’s [capabilities and limitations](https://github.com/Azure/apiforfhir-migration-tool/incremental-copy-docs/appendix.md).
73
72
#### Prepare Azure API for FHIR server
74
73
Identify data to migrate.
75
74
- Take this opportunity to clean up data or FHIR servers that you no longer use.
@@ -79,7 +78,7 @@ Identify data to migrate.
79
78
Deploy a new Azure Health Data Services FHIR Service server.
80
79
- First, deploy an Azure Health Data Services workspace.
81
80
82
-
- Then deploy an Azure Health Data Services FHIR Service server ([Deploy a FHIR service within Azure Health Data Services](/healthcare-apis/fhir/fhir-portal-quickstart.md)
81
+
- Then deploy an Azure Health Data Services FHIR Service server ([Deploy a FHIR service within Azure Health Data Services](fhir-portal-quickstart.md)
83
82
84
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 [migration tool documentation](https://microsoft.sharepoint.com/:w:/t/msh/Eb7WohSv_6JNlG1xAI8TyvoBbAPfhxnPzr4wv9py1InEww?e=QeSbo3&nav=eyJoIjoiMTUwODIzNzMifQ)). Configure the settings before you migrate.
85
84
@@ -97,7 +96,7 @@ Migrate applications that were pointing to the old FHIR server.
97
96
98
97
- Reconfigure any remaining settings in the new Azure Health Data Services FHIR Service server after migration.
99
98
100
-
- If you’d like to double check to make sure that the Azure Health Data Services FHIR Service and Azure API for FHIR servers have the same configurations, you can check both [metadata endpoints](/healthcare-apis/fhir/use-postman#get-capability-statement) to compare and contrast the two servers.
99
+
- If you’d like to double check to make sure that the Azure Health Data Services FHIR Service and Azure API for FHIR servers have the same configurations, you can check both [metadata endpoints](use-postman#get-capability-statement) to compare and contrast the two servers.
101
100
102
101
- Set up any jobs that were previously running in your old Azure API for FHIR server (for example, \$export jobs)
0 commit comments