Difference between revisions of "Inbound Folder"

Latest revision as of 18:44, 6 September 2017

• Start the FHIR server
• Determine the base url e.g. https://localhost.oridashi.com.au:8102
• Call to get server 'Metadata' information (this does not require credentials)
• Use C# WebCLient or HL7 FHIR C# reference libraries to make HTTP call
• HTTP call is:

 GET [base]/Metadata 

• Response is a "Conformance" resource http://hl7.org/fhir/DSTU2/conformance.html
• An extension has been added to provide the detected message delivery folder:

<Conformance>
   ...
   <extension url="http://oridashi.com.au/fhir/StructureDefinition/cis-inbound-folder">
       <valueString value="\\ORIDASHI-SERVER\hcnmsgs\In" />
   </extension>
  ...
</Conformance>

• The valueString will only be set if a read/writable folder exists
• This uses the following order of selection for the folder

 - manually configured (registry 'HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Oridashi' value string 'HL7Folder')
 - server share "Messages Share", "MessageShare", "MessagesShare"
 - default folder location based on the clinical system
 - BP is a special case and will always return "(correspondence-out)" as uses direct write

• If no valid folder found the entry will look like the following

<Conformance>
   ...
   <extension url="http://oridashi.com.au/fhir/StructureDefinition/cis-inbound-folder"/>
  ...
</Conformance>

• This extension value can be used to detect when a delivery folder can not be found
• When messages are delivered and an inbound folder can not be located the message will be delivered to a windows user folder where support can move the messages to the correct inbound folder when supporting the site. The local folder is:

<User Documents>\delivery-failed-message-box