URL Integration
PowerReader may be launched to open a specific patient or study by invoking it with an appropriate URL. User-specific login credentials can no longer be passed through the URL. Users are required to authenticate on the login page before the requested study is opened. These features effectively provide a unique URL for each patient and study in the RamSoft software. Parameters are supported through both HTTP GET and HTTP POST messages.
Multiple parameters in one URL call can be combined using the ampersand (&) symbol. For example, the URL below will open the study with Accession Number ACCECHO2 and Patient ID ID990023 after the user logs in:
When a URL is launched, the active PowerReader session is detected. . Username may be provided in the URL; however, password parameters in the URL are not supported. The system will always present the login page first. After successful authentication, the requested patient and/or study will be opened automatically using the URL parameters. If the specified patient and/or study are not present or not accessible by the logged in user, then the Search Worklist will be displayed.
The RamSoft PowerServer provides a special role type that was designed with URL integration in mind. The Public role permits multiple logins and denies access to the search list. Typically this role will be assigned to a group that has the Access to all studies privilege which permits access to any study in the system.
The following examples are provided here to help you understand the different URL integration scenarios.
Assumptions:
- User1 and User2 exist in PowerReader
- The Study exists in PowerReader and has Patient ID and Accession number information
Scenario 1: User1 is not yet logged into PowerReader and uses the URL (e.g. http://www.ramsoftpacs.com/powerreader/login.aspx?&username=USER1&app=powerreader&patientid=RAM12345&accessionnumber=12345). User1 logs in successfully into the portal page and Study 12345 with PatientID RAM12345 is opened in PowerReader.
Scenario 2: User1 has already logged into PowerReader and has a different study open in PowerReader. User1 closes the study and uses the URL (e.g. http://www.ramsoftpacs.com/powerreader/login.aspx?&username=USER1&app=powerreader&patientid=RAM12345&accessionnumber=12345 ) and Study 12345 with PatientID RAM12345 is opened.
Scenario 3: User1 has already logged into PowerReader; regardless of having launched PowerReader or not, User2 uses the URL with a specific username and study information (e.g. http://www.ramsoftpacs.com/powerreader/login.aspx?&username=USER2&app=powerreader&patientid=RAM34567&accessionnumber=34567). In this case, User 2 is able to log in through the portal contextually and PowerReader's context is changed from User1 to User2, thereby displaying the study with the relevant patient ID.
Scenario 4: User1 has already logged into PowerReader and is about to view a study; at the same time, User2 uses the URL with a specific username and study information (e.g. http://www.ramsoftpacs.com/powerreader/login.aspx?&username=USER2&app=powerreader&patientid=RAM34567&accessionnumber=34567). In this case, User 2 is able to log in through the portal and has the study with the specific PatientID opened in PowerReader and the Username now displaying "USER2".
For more information and examples of URLs, please refer to Section 2 of the RamSoft Client Integration Guide: http://software.ramsoft.com/dist/ramsoft/RamSoft%20Client%20Integration%20Specification%206.0.pdf