Currently Being Moderated

If your goal is to set up a proof of concept of the EMR Unwired solution (App & Mobile Server for Healthcare) this blog is meant for you. We provide a VM image which you can download and install & configure quickly.

In this blog post I would like to give you a step by step guide on how to set up the Mobile Server for Healthcare, connect your mobile device to the server and how to configure webservice calls so you can connect them to the backend of your choice.

All resources mentioned in this blog are tagged with "getting_started" so you can easily find them when walking through this blog / tutorial. You can find it by clicking on the tab "overview" and then "getting_started" in the tag cloud on the right side.

 

1) VM vs. full Mobile Server for Healthcare

There are two options of server installations you can chose from. One is to download a pre-packaged VM (virtual machine) which is described in this blog. The other is to install your own server. While the VM option is quick and easy to deploy it does not allow you to install new support packages (new functionality and fixes) or implement notes (single fixes). Additionally the VM has a limited time for usage as it is delivered with a test license which is only active for 90 days. Therefore we recommend you to install your own server for mid and longterm usage so you can benefit of fixes and new functionality as soon as we release them on the SAP Service Marketplace. For simplicity reasons this blog explains the setup with the VM with screenshots from an internal test run. For setting up a full server please see the EMR Administration Guide.

 

2) Download and installation of the VM

Open this link: https://store.sap.com/sap/cp/ui/resources/store/html/SolutionDetails.html?pid=0000000243&catID=&pcntry=DE&sap-language=E…

 

Download the three artifacts which you need in order to do the installation by clicking the three links:

- one for the .iso file: click the "Trial Version" button, fill out the form and download the iso.

- one for the operating system: open the section "Technical requirements" wherein you find the download for the SLES Linux version.

- one for the guide which will walk you through the installation step-by-step ("How to Guide"): see section "Technical requirements".

 

Here is a screenshot what you should see:

ScreenShot_TestTrialDownload.png

 

Please note: For good performance please consider the system requirements on the above download site.

 

After you walked through the documentation provided with the VM image you can proceed with step 3 to 9 which covers the EMR specific configurations.


3) Retrieval of host and port information (important for further configuration steps)

- Logon to the VM (Mobile Server for Healthcare)

- in the transaction field enter transaction "/nsicf"

- click on the execute icon (clock with green checkmark) or hit F8

- click on the grey icon to retrieve protocol, host & port –information

ScreenShot_SICF_Entry.png

- write down this information of protocol, host and port where port is equal to the column "Service"

ScreenShot_Port_Information.png

 

4) Test the connection from a browser to the Mobile Server

For a first test that the server is reachable via OData enter the following URL into the browser of you choice after replacing the host with your IP address.

http://<your_ip_or_host_name>:8042/sap/opu/odata/MEMR/MOBILE_EMR/$metadata

Example: http://10.55.148.206:8042/sap/opu/odata/MEMR/MOBILE_EMR/$metadata

An XML like metadata model of the EMR Objects should be returned

 

If this succeeds also check if demo data is retrievable via a REST client. To do so enter the following links into the REST client again after replacing the host with your IP.

http://<your_ip_or_host_name>:8042/sap/opu/odata/MEMR/MOBILE_EMR/PatientCollection('1')/Allergies?sap-client=001

Example: http://10.55.148.206:8042/sap/opu/odata/MEMR/MOBILE_EMR/PatientCollection('1')/Allergies?sap-client=001

Here is a screenshot as a reference with the result displayed with a REST client (here the firefox browser was used):

ScreenShot_REST_Client.png

Hints:

- After you send the request a popup will appear. Enter your user and password, e.g. developer / ch4ngeme.

- should you encounter the error "RFC error when sending logon data" go to transaction secstore, delete all entries and try again.

 

 

5) Test the connection from a mobile device to the Mobile Server

- Download and install the EMR mobile app on the device

- go to the app settings and make the following entries:

--> Backend URL = http://<your_ip_or_host_name>:8042/sap/opu/odata/MEMR/MOBILE_EMR

--> Client = 001

--> Sample Data Mode = disabled

 

6) Webservice Connectivity

The webservice definitions are provided with file "Webservice WSDLs.zip" which can be downloaded from our EMRU partner page: https://service.sap.com/~sapidb/011000358700001249782012E/. Please note: You can access this area only if you have become a SAP Partner, e.g. via www.sapmobileappspartnercenter.com.

 

You can use these to develop a backend adapter to expose this data to the Mobile Server.

 

Presuming the development is done the next step is configure the Mobile Server to connect to the webservices of the backend.

For the actual configuration please see section "Web Service based Service Interfaces" in the EMR Implementation Guide which can be downloaded from the EMRU partner page.

Note: If you launch the transaction "SOAMANAGER" from the VM, the browser-link will be generated with host "nplhost". If the host is not resolved, change it to "localhost" and the SOAManager should be launched properly.

 

After configuring the webservices you have to register the webservices to be called by the Mobile Server for data retrievel from the backend. To do so:

- from the "getting_started" section download the file "EMR WebService Configuration XML"

- logon to the Mobile Server

- enter the configuration UI by entering transaction "/n/MEMR/CONFIG_UI"

- go to change mode

- click the button "Import from local file"

- select the downloaded file (emrConfigWebServiceImplementation.xml)

- click the save icon to save your changes

 

Now the webservices should be called.

Comments

Actions

Filter Blog

By author:
By date:
By tag: