Using Noah Mobile Locally

When a Noah Mobile enabled Business System (Noah Server Remote Host) has been configured and enabled, it will be ready to securely respond to apps on the local area network.

Open

• When an App (Noah Mobile Client Application) wants to connect to the Business System (Noah Server Remote Host), the App must broadcast for Noah Server Remote Hosts on the local area network. All enabled Noah Servers on the network will respond to the broadcast with their Noah Mobile alias. In most cases, there will only be one Noah Mobile server enabled on a LAN. 

• The client application must contact the selected Remote Host through it's Local Noah Mobile WebAPI.
  Note: Noah Mobile will need an Internet connection to access Azure and resolve the Noah Server IP and redirect URI for the app.

  • When accessing a Remote Host locally there is only one valid Alias that can be used and this is the top Alias in the Noah Mobile configuration screen. When the Noah Server service is started it will use the top Alias as the Local Alias - none of the other Alias' can be used for Local discovery. The top Alias is also the one that is send to the app when replying to a broadcast request.

• The App must then authorize using the ‘Local Authorization Server’ to obtain an access token. The access token allows it to access the Local Noah Mobile WebAPI so it can access patient data from the  Noah Server. 

• Access tokens are valid for a limited period and the client application must acquire a new one upon expiration.