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
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,22 +32,21 @@ 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
-
|---**Capabilities**|---**Azure API for FHIR**|---**Azure Health Data Services**|||
|---**Capabilities**|---**Azure API for FHIR**|---**Azure Health Data Services**|
37
37
|**Settings**| Supported: Local RBAC • SMART on FHIR Proxy | Planned deprecation - Local RBAC (9/6/23) - SMART on FHIR Proxy (9/21/26) |||
38
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. |||
39
39
|**Data ingress**| Tools available in OSS | $import operation |||
40
40
|**Autoscaling**| Supported on request and incurs charge | Enabled by default at no extra charge |||
41
41
|**Search parameters**| - Bundle type supported: Batch - Include and revinclude, iterate modifier not supported - Sorting supported by first name, last name, birthdate and clinical date | - Bundle Type supported: Batch and transaction - Selectable search parameters - Include, revinclude, and iterate modifier is supported - Sorting supported by string and dateTime fields |||
42
42
|**Events**| Not Supported | Supported |||
43
-
|**Infrastructure**| Supported: - Customer managed keys - AZ support and PITR - Cross region DR | Supported - Data recovery - Upcoming: AZ support for customer managed keys |||
44
-
43
+
|**Infrastructure**| Supported: - Customer managed keys - AZ support and PITR - Cross region DR | Supported - Data recovery - Upcoming: AZ support for customer managed keys |||
45
44
46
45
### Things to consider that may affect your architecture
47
46
48
47
-**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)
49
48
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).
49
+
-**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).
51
50
52
51
-**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)
53
52
@@ -96,10 +95,10 @@ Migrate applications that were pointing to the old FHIR server.
96
95
97
96
- Reconfigure any remaining settings in the new Azure Health Data Services FHIR Service server after migration.
98
97
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.
98
+
- 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.md#get-capability-statement) to compare and contrast the two servers.
100
99
101
100
- Set up any jobs that were previously running in your old Azure API for FHIR server (for example, \$export jobs)
102
101
103
-
## Step 5: Cut over to Azure Health Data Services FHIR Services
102
+
## Step 5: Cut over to Azure Health Data Services FHIR services
104
103
105
104
After you’re confident that your Azure Health Data Services FHIR Service server is stable, you can begin using Azure Health Data Services FHIR Service to satisfy your business scenarios. Turn off any remaining pipelines that are running on Azure API for FHIR, delete data from the intermediate storage account that was used in the migration tool if necessary, delete data from your Azure API for FHIR server, and decommission your Azure API for FHIR account.
0 commit comments