Kofax provides an add-on pack for their Transformation Modules product to handle CMS-1500 (formerly HCFA) and CMS-1450 (alternatively, UB-04) medical claims forms called the KTM Medical Claims Add-on package. Related to this package is the Kofax Export Connector for Medical Claims. This Export Connector allows for the data captured off of said forms to be formatted in the HIPAA-compliant EDI/ASC X12 837 formats (to be exact, 837 Professional for the CMS1500 and 837 Institutional for the UB04).
ILINX Export supports the Microsoft Cluster Service (MSCS) for High Availability. MSCS provides the ability for a group of independent servers to be managed as single system. ILINX Export is a Cluster-Unaware Service and relies on the Generic Service Resource Type to manage services as a cluster.
I thought I would share out the following information because of how often it comes up. When dealing with Oracle WebCenter Content or WebCenter Imaging, it is good to know what restricted use licenses each product includes. The following guide from Oracle shows you what products are bundled together in the WebCenter Suite.
When you install ILINX Content Store or ILINX Capture, generally it is assumed you install the ADFS (Active Directory Federation Services) authentication provider and the ILINX Application on the same server. However, in the case that you are already using ADFS on another server for authentication, it is possible to use that separate instance of ADFS.
I ran into an interesting challenge with a customer and thought it might be something of interest to others. The challenge was in creating a way to have an entire batch of documents go through Advanced Capture processing and be returned to the input software, in this case ILINX Capture, as a single batch upon export.
For the past year, I’ve been working with a customer on a large Oracle BPM project. As part of the project there are a couple forms written using Oracle’s Application Development Framework (ADF.) I’d like to do a small series on this blog of useful techniques that have helped me with a successful implementation in a large scale production environment. Today, we’ll be talking about how to pass information from the ADF binding layer to a named parameter that is setup on a view object in the model layer. This comes up pretty often and there are some neat things you can do using the technique.
Let’s take a look at our view object first.
For this discussion we are using the HR sample schema that comes with an Oracle database. As you can see this view object uses a query that has a single bind variable that represents a department id. Its result set will be all the employees which belong to the supplied department. Our use case is going to be a table that will display employee information based on the department selected in a drop down list. There are many ways to do this type of thing in ADF and this isn’t necessarily the best use case for it but it has the advantage of being simple to follow and explain. We will talk a bit about some other uses for this technique later on. Continue reading