Configuring EpicIntegrations.config Settings - Signature Deficiencies for Epic - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - external

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

To configure Signature Deficiencies for Epic settings, complete these steps:

  1. Open EpicIntegrations.config.
  2. Between the epicDatasource tags, type the name of the OnBase data source configured on the OnBase Application Server.

    For example: <epicDatasource> DMS </epicDatasource>

    • This data source is used only if no data source is assigned to the environment ID received from Epic.

    • If the environment ID received from Epic is not mapped to a valid data source and the epicDatasource is blank or invalid, the integration uses the data source specified in the mapped Application Server's Web.config.

  3. Between the filterPhysiciansBySpecialty tags, type one of the following:

    • true —Set to allow analysts to find physicians by specialty.

    • false —Set to remove the option of searching by specialty from the Analysis window.

    For example: <filterPhysiciansBySpecialty> true </filterPhysiciansBySpecialty>

    If no valid value is specified, this setting is treated as false.

  4. Between the environmentID tags under <server>, type the Epic environment ID you want to map to a specific Application Server.
    For example: <environmentID> PRD </environmentID>
  5. Between the url tags, type the service path for the OnBase Application Server you are mapping to the environment ID.
    For example: <url> http://server/appserver/Service.asmx </url>
  6. Between the datasource tags (if present), type the name of the data source that should be used with this environment ID. Make sure the value matches the data source name configured on the specified server.

    For example: <datasource> ProdDMS </datasource>

    • The datasource element allows each environment ID to be mapped to a different data source. If the datasource element is absent, you can add it directly under the url tags within the server element.

    • If the datasource element is absent, blank, or invalid, Signature Deficiencies for Epic will use the configured epicDatasource value.

    • If the epicDatasource value is blank or invalid, Signature Deficiencies for Epic will use the dmsdatasource value configured in the Web.config of the Application Server mapped to the environment ID.

  7. To map additional environment IDs to specific Application Servers, do the following:
    1. Copy the entire server element (from the opening <server> tag through the closing </server> tag).
    2. Paste the copied server element between the closing </server> and </servers> tags.
    3. Configure the environment ID and Application Server URL as described in steps 4 and 6.
    4. Repeat these steps for each environment as needed.
      Note:

      If the data source or environment ID contains a <, >, or &, then the value must be enclosed within a <![CDATA[ ]]> section. Otherwise, the CDATA tags can be omitted. For example, if the environment ID is X&Y, then the environmentID element would use the following format: <environmentID><![CDATA[ X&Y ]]></environmentID>.

  8. Save EpicIntegrations.config. When you are finished, the file might resemble the following: