Intro to interopiO® Gateways

In interopiO, a gateway represents an API endpoint which surfaces FHIR and CDS Hooks functionality.  A gateway is backed by a data adapter which defines what data is surfaced through that gateway.  


Selecting a Default Data Adapter

When creating a gateway you'll be asked to select a default data adapter. This data adapter is the default source of data for answering all API calls that come through this gateway. You must choose a default data adapter during the gateway creation because it cannot be changed later. In addition to defining the data, it will also determine the user management strategy. A data adapter can have one of two types of user management:

  • Delegated Users - These are users which interopiO doesn't manage, but come from an external system. The only exposure interopiO has with these users is as they launch apps. 
    • The gateway must be authenticated with SMART on FHIR.
    • All launches of apps activated on this gateway will require a SMART launch proxy and must be initiated in the EHR.
    • May not activate patient or provider portals for these gateways.
  • interopiO Users - These users are managed inside interopiO, through the Authentication section of the admin console.  
    • Applying security on the gateway is optional.
    • May activate patient and provider portals which users can log into using the assigned user directory.

Once selected at creation time, the default data adapter cannot be updated.



Caching improves the performance of a gateway and is recommended in all production scenarios.  When caching is enabled there may be a delay between the time gateway configuration changes take place in the admin console and those changes taking effect in the associated gateway.  Because of this delay, it may be easier to keep the cache turned off during the initial configuration of your gateway.

You may manually flush the cache at anytime from the gateway details tab.

0 out of 0 found this helpful



Please sign in to leave a comment.