Difference between revisions of "Server Configuration"

From Hiasobi - FHIR
Jump to: navigation, search
Line 1: Line 1:
 
Hiasobi server configuration support two main uses
 
Hiasobi server configuration support two main uses
 
* define how you would like the server to run
 
* 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
 
* define how the server is running
 +
** Embedded - returned as actual configuration from '''Start''' call on '''Oridashi.Fhir.Host.FhirHost''' server
 +
** Standalone - serialized to file as reference for executable server (FHIR-HOST.exe)
  
  

Revision as of 12:48, 28 February 2014

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
    • Standalone - serialized to file as reference for executable server (FHIR-HOST.exe)


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 '*'
BestPracticePort8190Web server port for local Best Practice CIS
MedicalDirectorPort8191Web server port for local Medical Director CIS
ZedmedPort8192Web server port for local Zedmed 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
DeidentifyfalseRemove names and human identifiers for patients and providers