Difference between revisions of "Rhapsody Webcast Series: Rhapsody Webcast Series: Advanced Concepts"
(Created page with "Category:Webcasts __TOC__ ==Webcast Overview== Our previous webcast focused on the basic functionality of Rhapsody. This time we will explore some advanced concepts that...") |
(→Files) |
||
| Line 11: | Line 11: | ||
==Files== | ==Files== | ||
| − | [[Media:Rhapsody_Webcast_Series_Advanced_Concepts.pdf| Webcast | + | [[Media:Rhapsody_Webcast_Series_Advanced_Concepts.pdf| Webcast Slides]] |
== Links == | == Links == | ||
Revision as of 17:09, 7 October 2013
Webcast Overview
Our previous webcast focused on the basic functionality of Rhapsody. This time we will explore some advanced concepts that begin to demonstrate the power of Rhapsody. We will explore topics like web services, database calls, using multiple routes in one interface, and design concepts/best practices.
Q&A
Q. How does imaglelink work with Rhapsody?
A. I haven't researched this particular topic but nothing should really change. The base url or filepath is still defined within TWADmidmin workspaces within the ehr. The act of filing the unique identifers for a particular image to link to a particular result would still be handled within the FileResult_SP You would just be mapping the hl7 fields directly into the FileResult call as opposed to a FileResult message definition.