Scanning Integrations - Signature Deficiencies for Epic - English - Foundation 22.1 - OnBase - external

Signature Deficiencies for Epic
Platform
OnBase
Product
Signature Deficiencies for Epic
Release
Foundation 22.1
License

You can configure the Scan Acquisition Server (SAS) or Front Office Scanning (FOS) integration to connect to the correct OnBase system for import. When notifying Epic of a new document, the SAS or FOS integration sends Epic both the document handle and the Facility ID for the system where the document has been stored.

When integrating with Epic Hyperdrive using a SMART on FHIR launch of the SAS or FOS client, you can configure exact parameters for the location and environmentID elements in the command line interface. To launch the SAS or FOS client successfully, you must also configure exactly one matching value in the EpicIntegrations.config file for each of these elements provided on the command line. If neither element is provided on the command line, you must also remove these elements from the EpicIntegrations.config file.

To configure a SAS or FOS client launch:

  1. Open the EpicIntegrations.config file that resides in the same directory as the scanning DLLs for SAS or FOS.
  2. Locate the <servers> element under <OBEpicViewer>.
  3. Under <servers>, add or modify a <server> element to include the following child elements:

    Element

    Description

    location

    The location is a value provided by Epic. In a multi-facility system, Epic may associate each facility with a different location value.

    environmentID

    The environmentID is a value provided by Epic for the environment ID you want to map.

    url

    The url is the Application Server URL to connect to for the specified location.

    datasource

    The datasource is the name of the connection string to use on the specified Application Server.
  4. Using these child elements, map an Epic location to the appropriate OnBase data source.

    For example:

    <servers>
<server>
<location>Emergency Room West</location>
<environmentID>PRD</environmentID>
<url>https://server1/service.asmx</url>
<datasource>OB PRD</datasource>
</server>
<servers>
  5. When mapping an Epic location to the OnBase data source, also note the following:

    • You can use a combination of locations and environment IDs to archive documents to different OnBase systems. If Epic sends OnBase a location value and an environment ID that are mapped to different OnBase systems, then the system mapped to the location value will be used.

    • If a value contains a <, >, or &, then the value must be enclosed in CDATA tags. For example, if the location is X&Y, then the <location> element would use the following format: <location><![CDATA[ X&Y ]]></location>. Otherwise, the CDATA tags can be omitted.

  6. Repeat for each location being used with this SAS or FOS deployment.
  7. Save EpicIntegrations.config.