Server Configuration

From Hiasobi - FHIR
Revision as of 16:17, 13 September 2017 by Brett Esler (Talk | contribs)

Jump to: navigation, search

Hiasobi server configuration support two main uses

  • 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
  • define how the server is running
    • Embedded - returned as actual configuration from Start call on Oridashi.Fhir.Host.FhirHost server; find allocated ports
    • Embedded and Standalone - registry entries made under the current user key HKEY_CURRENT_USER\Software\Oridashi\Hiasobi\<profile name>
      • config: JSON string with configuration data as per below (licence key withheld)
      • iss: issuer is FHIR server endpoint e.g. https://localhost.oridashi.com.au:8249
      • running: is running status if started and stopped normally


PropertyDefaultDescription
ProfileName'default'Identifying name (is allocated for licensed users)
NetworkServerfalseAllows 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 (DSTU2)8290Web server port for local Best Practice CIS
MedicalDirectorPort (DSTU2)8291Web server port for local Medical Director CIS
ZedmedPort (DSTU2)8292Web server port for local Zedmed CIS
GeniePort (DSTU2)8291Web server port for local Genie for Windows CIS
MedtechPort (DSTU2)8291Web server port for local Medtech CIS
LicenseKey(null)Allocated license key for associated ProfileName; required for access to 'live' CIS data
IsLivefalseAccess to 'live' CIS data, default is samples only
IsOpenfalseRun as an 'open' server over HTTP otherwise is 'closed' run over 'HTTPS' and require authentication
DeidentifyfalseRemove names and human identifiers for patients and providers