Skip to content

Commit 0c1651e

Browse files
authored
Merge pull request #2988 from MicrosoftDocs/her-june-10
Hospital updates for June 10 release
2 parents 7a4c0da + 4cc2867 commit 0c1651e

29 files changed

+537
-48
lines changed

powerapps-docs/maker/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1696,6 +1696,8 @@
16961696
href: ../sample-apps/regional-emergency-response/portals-admin-reporting.md
16971697
- name: Portal for healthcare worker
16981698
href: ../sample-apps/regional-emergency-response/portals-user.md
1699+
- name: Transfer data from hospital to regional
1700+
href: ../sample-apps/emergency-response-data-transfer.md
16991701
- name: Learn from others
17001702
items:
17011703
- name: Blog
Lines changed: 260 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,260 @@
1+
---
2+
title: Transfer data from Hospital to Regional System | Microsoft Docs
3+
description: Provides information on transferring data from hospital to regional solution using SFTP server.
4+
author: pankajarora-msft
5+
manager: annbe
6+
ms.service: powerapps
7+
ms.topic: conceptual
8+
ms.custom:
9+
ms.date: 06/10/2020
10+
ms.author: pankar
11+
ms.reviewer: kvivek
12+
searchScope:
13+
- PowerApps
14+
---
15+
# Transfer data from Hospital to Regional System
16+
17+
Microsoft provides you the following solutions for emergency response:
18+
19+
- The *Hospital Emergency Response solution* enables you to collect data for situational awareness of available beds and supplies, COVID-19 related patients, staffing, and pending discharges at a **hospital level**.
20+
21+
- The *Regional Government Emergency Response and Monitoring solution* enables you to collect data for situational awareness of available beds and supplies, COVID-19 related patients, staffing, and pending discharges at a **regional health organization level**. Each hospital under the regional organization jurisdiction can submit their data by using the regional organization's portal, which is also part of the *Regional Government Emergency Response and Monitoring solution*.
22+
23+
Hospital Emergency Response solution customers can transfer their hospital data to the regional medical organizations that have Regional Government Emergency Response and Monitoring solution.
24+
25+
The out-of-box solution uses the Secure File Transfer Protocol (SFTP) as the data transmission mechanism. Customers can use other ways to transfer data to/from these solutions such as [importing and exporting data as CSV files](/powerapps/maker/common-data-service/data-platform-import-export) and [using web services](/powerapps/developer/common-data-service/work-with-data-cds) to programmatically interact with data in Common Data Service, which is the underlying data store for these solutions.
26+
27+
This article provides information about how to use SFTP to do the data transfer.
28+
29+
## How does the data transfer happen?
30+
31+
This is how the data transfer happens:
32+
33+
1. Hospitals can publish their data from the hospital solution, such as information about beds, supplies, equipment, and staff, to a folder in an SFTP server hosted by their regional medical organization. Hospitals can publish data on-demand or can schedule it.
34+
35+
2. The hospital data published in the folder on the SFTP server is automatically downloaded to the regional solution and is used to create respective data records (beds, supplies, equipment, and staff) for the hospital in the regional solution.
36+
37+
## Prerequisites
38+
39+
These are the prerequisites for the data transfer to work successfully.
40+
41+
- **SFTP server**: The regional health organization must have an SFTP server configured with a folder for each hospital on the SFTP server where the hospital can publish their data. The hospital must get the credentials from regional health organization to connect to the folder on the SFTP server.<br/>
42+
For information about creating an SFTP server, see [SFTP on Azure](https://docs.microsoft.com/samples/azure-samples/sftp-creation-template/sftp-on-azure/)
43+
44+
- **CDC Short Name**: Each **Supply** and **Staffing Type** record must have the **CDC Short Name** value. You can create and manage these records in the **Admin app** of hospital and regional solutions.
45+
46+
- **DOH Number**: Each **Facility** record must have a valid **DOH Number** value. You can create and manage these records in the **Admin app** of hospital and regional solutions.
47+
48+
## Configure your solutions for data transfer
49+
50+
IT admins need to perform some steps to configure the data transfer from Hospital Emergency Response solution to SFTP server and from SFTP server to Regional Government Emergency Response and Monitoring solution.
51+
52+
> - [Step 1: Create connections](#step-1-create-connections)
53+
> - [Step 2: Enable flows for publishing data to SFTP (Hospital)](#step-2-enable-flows-for-publishing-data-to-sftp-hospital)
54+
> - [Step 3: Specify the data publish schedule (Hospital)](#step-3-specify-the-data-publish-schedule-hospital)
55+
> - [Step 4: Enable flow for pulling hospital data from SFTP (Regional)](#step-4-enable-flow-for-pulling-hospital-data-from-sftp-regional)
56+
57+
### Step 1: Create connections
58+
59+
Both the hospital and regional systems use Power Automate flows to transfer data between the hospital/regional solutions and SFTP server. In this step, we will create connections for Common Data Service and SFTP to be used by flows for data transfer.
60+
61+
This step is required for both hospital and regional solutions.
62+
63+
> [!IMPORTANT]
64+
> Make sure that you create connections in your Power Apps environment before installing the hospital and regional emergency response solutions or upgrading to the latest version. This will save you a lot of steps later while enabling flows that get installed as part of these solutions.
65+
66+
1. Sign in to [Power Apps](https://make.powerapps.com).
67+
68+
1. From the top-right corner, select your hospital or regional environment.
69+
70+
1. From the left navigation pane, expand **Data** and select **Connections**.
71+
72+
1. Select **New Connection**, and then type **Common Data Service** in the search box.
73+
74+
1. From the search results, select **+** next to **Common Data Service** connector to add a connection.
75+
76+
> [!div class="mx-imgBorder"]
77+
> ![Common Data Service connector](media/cds-connector.png)
78+
79+
1. On the next screen, select **Create**. Select or specify the credentials to create the connector. On successful authentication, your connection will be created.
80+
81+
1. Select **New Connection**, and then type **Common Data Service** in the search box.
82+
83+
1. From the search results, select **+** next to **Common Data Service (current environment)** connector to add a connection.
84+
85+
1. On the next screen, select **Create**. Select or specify the credentials to create the connector. On successful authentication, your connection will be created.
86+
87+
1. Select **New Connection**, and then type **SFTP** in the search box.
88+
89+
1. From the search results, select **+** next to **SFTP - SSH** connector to add a connection.
90+
91+
> [!div class="mx-imgBorder"]
92+
> ![SFTP connector](media/sftp-connector.png)
93+
94+
1. In the **SFTP - SSH** dialog box, provide the credentials to connect to the folder on the SFTP server. These details would have been already provided to you by your regional health organization as mentioned earlier in the **Prerequisites** section.
95+
96+
1. Select **Create**. Power Apps validates the connection details, and on successful authentication, creates an SFTP connection.
97+
98+
At the end of this step, you should have three connections: two for Common Data Service and one for SFTP.
99+
100+
### Step 2: Enable flows for publishing data to SFTP (Hospital)
101+
102+
This step has to be performed by the admins of the Hospital Emergency Response solution after they have installed the solution.
103+
104+
In this step, we will enable the following flows that will publish reviewed data from the hospital solution to SFTP server on a set schedule and on-demand:
105+
- Publish Bed Census Data
106+
- Publish COVID Data
107+
- Publish Data for All Facilities
108+
- Publish Equipment Needs Data
109+
- Publish Staff Updates
110+
- Publish Supply Item Details
111+
- Update Sync Census
112+
- Update Sync Equipment Needs
113+
114+
To enable these flows:
115+
116+
1. Sign into [Power Automate](https://flow.microsoft.com/).
117+
118+
1. From the left pane, select **Solutions.** From the solution list, select **Hospital Emergency Response Solution** to open the solution.
119+
120+
1. In the solution, filter on **Flow** to find all the flows.
121+
122+
> [!div class="mx-imgBorder"]
123+
> ![All flows](media/all-flows-hospital.png)
124+
125+
1. Select a flow name to open the flow definition. For example, select **Publish Bed Census Data**.
126+
127+
1. Select **Edit** on the toolbar and verify the embedded connections for this flow. These should be the same connections that you created earlier.
128+
129+
1. Select **Save** to save the changes, and then select **Turn On**.
130+
131+
1. Repeat steps 4-6 for other flows listed earlier.
132+
133+
If you face any issues working with flows, try [Troubleshooting a flow](https://docs.microsoft.com/power-automate/fix-flow-failures).
134+
135+
### Step 3: Specify the data publish schedule (Hospital)
136+
137+
The **Publish Data for All Facilities** flow contains the information about the data publish schedule. You can define the recurrence schedule when the flow will run automatically and publish the data that you have reviewed and marked as ready for publish.
138+
139+
1. Sign into [Power Automate](https://flow.microsoft.com/).
140+
141+
1. From the left pane, select **Solutions.** From the solution list, select **Hospital Emergency Response Solution** to open the solution.
142+
143+
1. In the solution, search for "Publish Data for". The **Publish Data for All Facilities** flow appears in the search result.
144+
145+
> [!div class="mx-imgBorder"]
146+
> ![Publish Data for All Facilities flow](media/publish-all-data-flow.png)
147+
148+
1. Select the flow name to open the flow definition, and then select **Edit** in the toolbar.
149+
150+
1. In the flow definition, select **Recurrence** and then select **Edit**.
151+
152+
> [!div class="mx-imgBorder"]
153+
> ![Update the data publish recurrence schedule](media/update-publish-schedule1.png)
154+
155+
1. Specify the data publish recurrence schedule.
156+
157+
> [!div class="mx-imgBorder"]
158+
> ![Update the data publish recurrence schedule](media/update-publish-schedule2.png)
159+
160+
1. Select **Save** to save your changes.
161+
162+
### Step 4: Enable flow for pulling hospital data from SFTP (Regional)
163+
164+
This step has to be performed by the admins of the Regional Government Emergency Response and Monitoring solution.
165+
166+
In this step, we will enable the **Create Record when a File is Created in SFTP Location** flow that will automatically create a record for hospital in the regional solution based on the data uploaded from the hospital system in the SFTP server.
167+
168+
> [!IMPORTANT]
169+
> For each hospital registering with regional organization to send data, the regional admins will need to do one of the following to ensure data for each hospital is copied from the SFTP server to the regional solution:
170+
>
171+
> - Copy data from all the hospitals to a single folder on the SFTP server to enable the **Create Record when a File is Created in SFTP Location** flow to copy all the data.
172+
>
173+
> - Create a copy of the **Create Record when a File is Created in SFTP Location** flow for each Hospital registering with them to send data, and in each flow instance change the SFTP server folder path as per the hospital. We'll show you how to do this later in this section.
174+
175+
1. Sign into [Power Automate](https://flow.microsoft.com/).
176+
177+
1. From the left pane, select **Solutions.** From the solution list, select **Regional Emergency Response Solution** to open the solution.
178+
179+
1. In the solution, filter on **Flow** to find all the flows.
180+
181+
> [!div class="mx-imgBorder"]
182+
> ![Flows in the app](media/conf-all-flows.png "Flows in the app")
183+
184+
1. Select the **Create Record when a File is Created in SFTP Location** flow to open the flow definition.
185+
186+
1. Verify the embedded connections for this flow. These should be the same connections that you created earlier.
187+
188+
1. Select **Save** to save the changes, and then select **Turn On**.
189+
190+
1. If regional admins are expecting data from multiple hospitals that are stored in different folders on SFTP server, they can create copies of the **Create Record when a File is Created in SFTP Location** flow to create one for each hospital, and update the SFTP folder name accordingly in the copied flow instance. To do this:
191+
192+
1. Select **Save As** on the toolbar to create a copy of the flow.
193+
194+
1. Rename the flow accordingly and save it. This flow will become available under **My flows**.
195+
196+
1. Select the flow to open it for editing. Select **Edit** on the toolbar.
197+
198+
1. Select **When a file is added or modified**, and select appropriate value in the **Folder** field:
199+
> [!div class="mx-imgBorder"]
200+
> ![Edit the flow](media/edit-flow.png "Edit the flow")
201+
202+
1. Select **Save** to save the changes, and then select **Turn On**.
203+
204+
205+
## Review and publish data to SFTP
206+
207+
After your IT admin has configured the solution for data transfer from the hospital solution, you can use the **Review and Publish Data** model-driven app to review the data and mark it as completed for publishing to the folder on the SFTP server.
208+
209+
1. Sign in to [Power Apps](https://make.powerapps.com).
210+
211+
1. From the top-right corner, select your hospital environment.
212+
213+
1. Select **Apps** in the left navigation pane, and then select the **Review and Publish Data** app.
214+
215+
1. In the app, all the facilities are listed. Select a facility for which you want to review the data and publish. This will open the facility record.
216+
217+
> [!div class="mx-imgBorder"]
218+
> ![Facility review](media/facility-review.png)
219+
220+
1. Scroll down the page to review the following data for your facility: Bed Census, COVID Stats, Equipment Needs, Supply Tracking, and Staff Updates. If necessary, update the data in grids, and then select the save icon to save your changes.
221+
222+
> [!div class="mx-imgBorder"]
223+
> ![Update values](media/update-values.png)
224+
225+
1. Once reviewed, you can select a row of data, and select **Mark Complete**. Select **OK** in the confirmation dialog box to complete the action.
226+
227+
The record's review status changes to **Completed**.
228+
229+
> [!div class="mx-imgBorder"]
230+
> ![Review completed](media/review-completed.png)
231+
232+
The scheduled flows will pick up the completed items for publishing to the SFTP folder that you configured earlier ([Step 3: Specify the data publish schedule (Hospital)](#step-3-specify-the-data-publish-schedule-hospital)).
233+
234+
### Manually publish data
235+
236+
The scheduled flow publishes data at a certain time, but what if you want to manually or immediately publish the data after reviewing it.
237+
238+
1. In the **Review and Publish Data** app, select the record that you want to publish from the **Published History** in the left pane. All the published data for the selected entity are displayed. If you want to view the active records for the entity, use the view selector.
239+
240+
> [!div class="mx-imgBorder"]
241+
> ![Review completed](media/manual-data-publish.png)
242+
243+
1. In this case, we will publish the data that we reviewed in the previous section. So, select the **Active Bed Census** view, select the row that was marked as completed, and then select **Flow** > **Publish Bed Census Data**.
244+
245+
> [!div class="mx-imgBorder"]
246+
> ![Manually run flow](media/manually-run-flow.png)
247+
248+
1. On the next screen, review that the connections are valid, and select **Continue**.
249+
250+
> [!div class="mx-imgBorder"]
251+
> ![Manually run flow](media/publish-data-flow.png)
252+
253+
1. On the next screen select **Run flow**. A message appears stating that the flow run started successfully and how you can monitor the progress.
254+
255+
## Issues and feedback
256+
257+
- To report an issue with the Hospital Emergency Response sample app, visit <https://aka.ms/emergency-response-issues>.
258+
259+
- For feedback about the Hospital Emergency Response sample app, visit <https://aka.ms/emergency-response-feedback>.
260+

0 commit comments

Comments
 (0)