Detect Endpoints

Detecting Hiasobi FHIR service when running as embedded and standalone can be done via 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 table above (licence key suppressed)
• 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

Example:

[HKEY_CURRENT_USER\Software\Oridashi\Hiasobi\oridashi]
"iss"="https://localhost.oridashi.com.au:8102"
"config"="{\"Mode\":\"BP\",\"ProfileName\":\"oridashi\",\"AuthPort\":8101,\"AutoPort\":8102,\"BestPracticePort\":8290,\"MedicalDirectorPort\":8291,\"Medtech32Port\":8293,\"GeniePort\":8294,\"ZedmedPort\":-1,\"IsLive\":false,\"IsOpen\":false,\"NetworkServer\":false,"OridashiVersion":"2.3.66.0"}"
"running"="true"
"pid"=dword:000007fd

2) Check service is running

• if value 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 https://

  GET <url>/Metadata

  (no credentials required)

• If passed then the FHIR service is available on the iss URL.
• Credentials are required to gain access the full API i.e. Oridashi allocated profile basic credentials or SMART on FHIR bearer token.