To determine whether the Integration for Epic Tapestry solution is a good fit for your environment, see the following questions:
- How many contexts does your Epic Tapesty solution use? Do you only use the
Document Linker context, or do you also use the
Create UB, Create Claim, and
CRM Request contexts?
Solutions that only use the Document Linker context will not need to use the additional Workflow actions created to support manual assignment to the Create UB, Create Claim, and CRM Request contexts.
If your system does not use one or more Epic Tapestry context, you will need to disable the Workflow rules under the Link to Epic/DocLink task for that context (Is Document CMS Claim Creation?, Is Document UB Creation?, and Is Document CRM Creation?)
- Are all documents in a Document Type Group related to a single Epic Tapestry
context?
If your system uses a single Document Type Group to store documents that should relate to multiple Epic Tapestry contexts, your users will not be able to use the Link to Epic/DocLink task to automatically assign the document to the appropriate Epic Tapestry context. Instead, you will need to enable the optional Create Claim, Create CRM Request, and Create UB tasks so that the user will be able to manually route each document to the appropriate context.
- Does your OnBase system integrated with multiple
Epic instances (for instance, a test environment and a production environment)?
If so, you can enable the optional Find EnvironmentID Props Workflow rule to determine which Epic environment the document should be linked to. This evaluates a specific Keyword Type to check if the environment is a test or production environment. For example, by default it is configured to check the HBI - Import Keyword Type for the word test. If true, the environment properties can be set to the values for your Epic test environement. If false, the environment properties can be set to the values for your Epic production environment.