Skip to content

Commit d259f3a

Browse files
shellyhaverkampshellyhaverkamp
committed
added last fwdlink
1 parent 12a807f commit d259f3a

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

‎articles/healthcare-apis/fhir/migration-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,5 +57,5 @@ Start with [migration strategies](migration-strategies.md) to learn more about A
5757

5858
Check out these resources if you need further assistance:
5959

60-
- Get answers from community experts in [Microsoft Q&A](https://learn.microsoft.com/answers/tags/389/azure-health-data-services).
60+
- Get answers from community experts in [Microsoft Q&A](https://go.microsoft.com/fwlink/?linkid=2248420).
6161
- If you have a support plan and require technical support, [contact us](https://ms.portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview).

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -61,10 +61,10 @@ If you want to migrate existing IoT connector device FHIR data from your Azure A
6161

6262
First, create a migration plan. We recommend the migration patterns described in the table. Depending on your organization’s tolerance for downtime, you may decide to use certain patterns and tools to help facilitate your migration.
6363

64-
| Migration Pattern | Details | How? |
65-
|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
64+
| Migration Pattern | Details | How? |
65+
|---|---|---|
6666
| 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.
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.|
6868

6969
### OSS migration tool considerations
7070

0 commit comments

Comments
 (0)