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
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,13 +35,13 @@ Compare the differences between Azure API for FHIR and Azure Health Data Service
35
35
36
36
|**Capabilities**|**Azure API for FHIR**|**Azure Health Data Services**|
37
37
|---|---|---|
38
-
|**Settings**| Supported: Local RBAC • SMART on FHIR Proxy | Planned deprecation - Local RBAC (9/6/23) - SMART on FHIR Proxy (9/21/26) |||
38
+
|**Settings**| Supported: <br>• Local RBAC <br>• SMART on FHIR Proxy | Planned deprecation <br>• Local RBAC (9/6/23) <br>• SMART on FHIR Proxy (9/21/26) |||
39
39
|**Data storage Volume**| More than 4 TB | Current support is 4 TB. Reach out to CSS team if you need more than 4 TB. |||
40
40
|**Data ingress**| Tools available in OSS | $import operation |||
41
41
|**Autoscaling**| Supported on request and incurs charge | Enabled by default at no extra charge |||
42
-
|**Search parameters**|- Bundle type supported: Batch <br> - Include and revinclude, iterate modifier not supported <br> - Sorting supported by first name, last name, birthdate and clinical date |- Bundle Type supported: Batch and transaction <br> - Selectable search parameters <br> - Include, revinclude, and iterate modifier is supported <br> - Sorting supported by string and dateTime fields |||
42
+
|**Search parameters**|• Bundle type supported: Batch <br> • Include and revinclude, iterate modifier not supported <br> • Sorting supported by first name, last name, birthdate and clinical date |• Bundle Type supported: Batch and transaction <br> • Selectable search parameters <br> • Include, revinclude, and iterate modifier is supported <br>• Sorting supported by string and dateTime fields |||
43
43
|**Events**| Not Supported | Supported |||
44
-
|**Infrastructure**| Supported: - Customer managed keys <br> - AZ support and PITR <br> - Cross region DR | Supported - Data recovery <br>- Upcoming: AZ support for customer managed keys |||
44
+
|**Infrastructure**| Supported: - <br> • Customer managed keys <br> • AZ support and PITR <br> • Cross region DR | Supported - Data recovery <br> Upcoming: AZ support for customer managed keys |||
45
45
46
46
### Things to consider that may affect your architecture
47
47
@@ -63,8 +63,8 @@ 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](../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://go.microsoft.com/fwlink/?linkid=2247964) 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. |
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://go.microsoft.com/fwlink/?linkid=2248131) to help with this migration pattern. Or, create your own tool to migrate the data incrementally.
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: <br> • 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. <br> • The [GitHub repo](https://go.microsoft.com/fwlink/?linkid=2247964) provides tips on running these commands, and a script to help automate creating the \$import payload. <br> • Or create your own tool to migrate the data using \$export and \$import. |
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. <br> • We created an [OSS migration tool](https://go.microsoft.com/fwlink/?linkid=2248131) to help with this migration pattern. <br> • Or create your own tool to migrate the data incrementally.
0 commit comments