Difference between revisions of "FHIR Introduction Package"

From Hiasobi - FHIR
Jump to: navigation, search
(SMART on FHIR)
(Oridashi-Hiasobi Adapters)
Line 5: Line 5:
 
== Oridashi-Hiasobi Adapters ==
 
== Oridashi-Hiasobi Adapters ==
 
* Applications run on the clinical desktop as "Oridashi-Hiasobi adapters"
 
* Applications run on the clinical desktop as "Oridashi-Hiasobi adapters"
 +
* Adapters can be custom branded and include custom features as needed
 
* Adapters are started on windows login and run in the users windows session
 
* Adapters are started on windows login and run in the users windows session
 
* Core adapter support includes hosing secured FHIR servers for all clinical products
 
* Core adapter support includes hosing secured FHIR servers for all clinical products

Revision as of 09:20, 11 March 2016

FHIR DSTU2 Support

  • Draft standard for trial use 2 is the nominal supported version for Hiasobi as per http://hl7.org/fhir/DSTU2/index.html
  • Check the [base]/metadata content of Hiasobi servers for details of specific resource and search parameter support.

Oridashi-Hiasobi Adapters

  • Applications run on the clinical desktop as "Oridashi-Hiasobi adapters"
  • Adapters can be custom branded and include custom features as needed
  • Adapters are started on windows login and run in the users windows session
  • Core adapter support includes hosing secured FHIR servers for all clinical products
  • Automatic or manual selection of the clinical system is supported
  • Manual switch to 'samples' supported for evaluation and testing
  • Click-once deployed into user profile (no admin)

SMART on FHIR

  • Oridashi-Hiasobi implements the SMART-on-FHIR Authorisation profile http://docs.smarthealthit.org/authorization/
  • Hiasobi supports a local Auth server interface to enable authorisation
  • OAuth2 authorisation challenge is made to establish access
  • Authorisation can only occur when a user is logged into the clinical system
  • Specific authorisation of requested resources and context is made and recorded in the user profile
  • A unique token is supplied to the web application to use for access to the local FHIR service