Difference between revisions of "Server Configuration"
From Hiasobi - FHIR
Brett Esler (Talk | contribs) |
Brett Esler (Talk | contribs) (→Configure FHIR Service) |
||
| Line 24: | Line 24: | ||
<tr><td>Deidentify</td><td>false</td><td>Remove names and human identifiers for patients and providers </td></tr> | <tr><td>Deidentify</td><td>false</td><td>Remove names and human identifiers for patients and providers </td></tr> | ||
</table> | </table> | ||
| + | |||
| + | |||
| + | . | ||
= Detecting FHIR Service Location = | = Detecting FHIR Service Location = | ||
Revision as of 17:13, 13 September 2017
Configure FHIR Service
Hiasobi server configuration support two main uses:
1) define how you would like the server to run
- Embedded - passed in as Oridashi.Fhir.Configuration object in Start call on Oridashi.Fhir.Host.FhirHost server
2) define how the server is actually running
- Embedded - returned as actual configuration from Start call on Oridashi.Fhir.Host.FhirHost server; find allocated ports
| Property | Default | Description |
|---|---|---|
| ProfileName | 'default' | Identifying name (is allocated for licensed users) |
| NetworkServer | false | Allows network calls from other machines to this server, default is to only allow the local machine |
| AcceptedCrossOrigins | (null) | Domains (string array) specifically allowed Cross Origin Resource Sharing domains for browser based calls; default (null) is any domain '*' |
| BestPracticePort | 8290 | Web server port for local Best Practice CIS |
| MedicalDirectorPort | 8291 | Web server port for local Medical Director CIS |
| ZedmedPort | 8292 | Web server port for local Zedmed CIS |
| GeniePort | 8291 | Web server port for local Genie for Windows CIS |
| MedtechPort | 8291 | Web server port for local Medtech CIS |
| LicenseKey | (null) | Allocated license key for associated ProfileName; required for access to 'live' CIS data |
| IsLive | false | Access to 'live' CIS data, default is samples only |
| IsOpen | false | Run as an 'open' server over HTTP otherwise is 'closed' run over 'HTTPS' and require authentication |
| Deidentify | false | Remove names and human identifiers for patients and providers |
.
Detecting FHIR Service Location
Embedded and Standalone - registry entries made under the current user key
1) Check registry for last known service details
HKEY_CURRENT_USER\Software\Oridashi\Hiasobi\<profile name>
Profile name is your company/product id allocated by Oridashi.
config: JSON string with configuration data as per below
- iss: issuer is FHIR server endpoint e.g. https://localhost.oridashi.com.au:8249
- running : is running status if started and stopped normally
- pid: process identifier of host application/service
2) Check service is running
- if running == false then FHIR service is NOT running (if true need to check further)
- if process with id pid is not running for the current user then the FHIR service is NOT running (if found then check further)
- iss is URL for FHIR service a should respond to
GET <url>/Metadata
(no credentials required)
If passed then the FHIR service is available on the iss URL. Credentials are required to gain access i.e. allocated profile basic credentials or SMART on FHIR bearer token.
