Medical Data Storage and Display Part 3

[#1]

• Step 7: Access Data
• Step 8: Test Application
• Step 9: Next Steps

Step 7: Access Data

Now that we have a basic display in-place, we need to access the backend data.

To do so, we'll make use of built-in Mashup Data Services.

1. At the top-right, ensure that the Data tab is selected.
   
   
   
2. Click the green + button.
   
   
   
3. In the Entities Filter field of the Add Data Pop-up, search for and select MDSD_Thing.
4. In the Services Filter field, type getprop.
5. Click the arrow beside GetProperties.
   • Note that the GetProperties() Service has been added to the right section.
6. Check the Execute on Load checkbox.
   
   
   

7. At the bottom-right of the pop-up, click Done.

   • Note how the GetProperties() Mashup Data Service has been added to the top-right under the Data tab.
     
     
   

Bind Info Table Property

Now that we have access to the Data Service within the Mashup, we'll use it to pull backend data into the Mashup (specifically, the aggregated Info Table Property), and then bind it to the Grid Widget.

1. Expand the GetProperties Service.
   
   
   
2. Drag-and-drop MDSD_InfoTable_Property onto the Grid Advanced Widget.
   
   
   
3. On the Select Binding Target Pop-up, select Data.
   
   
   
4. Note how the bottom-center Connections Window indicates that the aggregated Info Table Property is now bound to the grid.

 

Access the Aggregation Service

Because we selected the Execute on Load option for GetProperties(), the Service will grab the information from the aggregated Info Table Property and propagate that into the Grid Advanced Widget on initially opening the Mashup in a web browser.

However, we currently have no way to call our custom aggregation Service besides diving into the backend as we did when we first created it and performed testing.

Instead, we want the Mashup itself to have the ability to call the aggregation Service.

We'll do so via the Button Widget's Clicked Event, but we first need to gain access to our custom Service in the Mashup.

1. In the top-right Data tab beside Things_MDSD_Thing, click the green </> button.

   • Note that the Add Data Pop-up opens with the MDSD_Thing pre-selected.
     
     
   

2. On the left of the Add Data Pop-up, expand Select Service Category, and choose **Uncategorized**.

   • Note our custom MDSD_Aggregation_Service.
     
     
   

3. Beside MDSD_Aggregation_Service, click the right arrow to add it to the Selected Services section.

   • Note that we do NOT want to check "Execute on Load", because don't want the Service called upon initially opening the Mashup in a web browser.
     
     
   

4. At the bottom-right, click Done.

   • Note the MDSD_Aggregation_Service has been added to the far-right Data tab.
     
     
   

Bind Button to Aggregation Service

Now that we can reference the aggregation Service in the Mashup, we'll bind it to pressing the Button Widget.

1. Click the Button Widget to select it.
   
   
   
2. Click the top-left of the Button Widget to reveal the Drop Down Menu.
   
   
   
3. Drag-and-drop the Clicked Event onto the MDSD_Aggregation_Service under the Data Tab.
   
   
   
4. On the bottom-right, with the MDSD_Aggregation_Service selected, drag-and-drop the MDSD_Aggregation_Service's ServiceInvokeCompleted Event onto GetProperties in the Data Tab.
   • This causes the completion of the aggregation Service to re-call GetProperties, which updates the grid; as such, a new entry into the Info Table Property created by the custom Service will immediately show up in the Grid Widget.
5. In the top-right, click the GetProperties Service to see all of its interactions in the bottom-center Connections window.
   
   
   
6. At the top, click Save.

Step 8: Test Application

Our MVP MRI Service Application is now complete.

Let's test it.

1. At the top, click View Mashup.

   • Note the pre-existing single entry from our Service test which we executed directly from the backend.
     
     
   
2. Click Retrieve MRI Statistics.
   
   
   
3. Wait a moment and click Retrieve MRI Statistics again.
   • Note that each click adds another entry to the Grid Widget.

Each time that you press the Button Widget, what you're really doing is calling our custom aggregation Service in the Foundation backend.

This Service then goes out and pulls in information from our various EMS-connected Edge sub-systems.

To add additional sub-systems (maybe a "friction" detection on the patient-bed indicating that it needs additional grease) all you would have to do is repeat the steps in this Learning Path, i.e. connect the additional sub-system with the EMS, add another Field Definition to the Data Shape, and modify the aggregation Service to retrieve that info and store it in the Info Table Property.

In addition, you may wish to improve the GUI. Rather than using a Positioning: Static Mashup, you could utilize a Responsive setup, sub-divide the Canvas into various sections, and then add items such as your company's logo. This would also make the GUI more friendly to different screen resolutions.

You can even add business logic to the Mashup itself. For instance, the Auto Refresh Widget (Legacy) can effectively be used as a "timer". In the same way that the Button Widget's Clicked Event calls the aggregation Service, the Auto Refresh Widget could be used to trigger the Service call at a set interval. Then, as long as the Mashup was open, the Button Widget would only be needed when you wanted an immediate status update.

For more information on implementing additional business logic, refer to the Create Custom Business Logic guide.

Or the Time Selector Widget could be used to restrict the information in the Grid Widget to only the timeframe you wanted to investigate.

Step 9: Next Steps

Congratulations! You've successfully completed the Medical Data Storage and Display guide, and learned how to:

• Create a Data Shape and Info Table Property to store Medical Data
• Create a Service to combine data from multiple Edge devices into a single, logical Thing
• Create a Mashup to view and retrieve Medical data

This is the last guide in the Medical Device Service learning path.

Learn More

We recommend the following resources to continue your learning experience:

 Capability     Guide

Build	Methods for Data Storage
Experience	Create Your Application UI

 

Additional Resources

If you have questions, issues, or need additional information, refer to:

 Resource       Link

Community	Developer Community Forum
Support	ThingWorx Help Center