IntelliSoft Group Blog

by Mike Aha

We receive a great number of program modification requests from our customers, some simple and easy to implement, and others that are fairly complicated.  We appreciate and welcome all such requests, as it is important for us to know what your needs are.  Requests are reviewed periodically as part of the Development planning process.

As is normal with any software company, we receive more requests than we can complete from version to version.  This requires us to make decisions on which modifications to complete.  The development planning process takes a lot of things into consideration: customer requests, industry changes, sales input, technology changes, etc.  The decision to include a request in the development plan for a version is based primarily on development time investment vs. value created for the most customers.

 As an individual customer’s usage of the IntelliSoft programs varies depending on their internal processes, a particular request may be something that is applicable to a large number of other users, or only a few.  The development time required to complete features can vary widely.  Something that appears to be simple can actually be fairly complicated in terms of coding, data creation or testing. 

Significant modifications that benefit few customers tend to remain lower priority in the development queue.  Paid customization may be a consideration for customers with modifications of this kind.  Because of the length of the development cycle, minimum turnaround time on a request is typically 6 months to a year, though it is possible for minor changes to be made more quickly.  Lower priority/nice-to-have modifications may take significantly longer to be implemented.

Due to the volume of requests received, customers typically are not notified about the status their requests other than for customizations. However we are planning to implement the ability to make and view requests on our website, possibly in the first quarter of next year.

by Mike Aha

We have released version 10.2 and the download is on our Website.  This is a minor release that replaces 10.1, adding a few functionalities requested by IntelliApp users.  These were planned for the January 10.5 version, but were deemed important enough that they were migrated into the current release.

1- Editing Applications after populating:  From Application Printing,  the ability now exists to edit an application after it is populated, but before it is printed, emailed, etc.  Populated fields can be removed, and text fields can be added.  To enable editing, check the Edit Before Printing checkbox before clicking and of the Populate button..

2- Start at character mapping function:  In application mapping we have added a mapping field property to allow populating substrings of the data.  This has been added primarily to allow the mapping of individual characters of a data value on a form, for example a Medicaid application requiring the characters of the NPI number to be placed in individual boxes on the form.  It could also be used, for example, for getting the last four digits of an SSN.

3- Batch Add Applications Action Types: In the Batch Add Applications window, we have added some new functionalities.  First is ability to select the Action Type to be created.  The default will still be App Out to MD, but another may be selected if desired.  Also added is the ability to add a note to each Action record, and to complete the Action as it is created.  This can allow, for example, the creation of a completed follow-up action for a number of practitioners at the same time.

You can see the details of these functionalities in the 10.2 release notes document on our Website.

By Mike Aha

While many of you are getting your feet wet with V10.1 renaissance, the development team is working on the next version.  Continuing with the Renaissance theme of making the program functionality simpler, more productive and more intuitive, one of the areas we are working on is Application Mapping.  Here are some of the plans:

Converting the separate Screens and fields windows into a single Tree-view.  Click to open a screen and see the fields listed under the screen, using the field labels defined from your Screen Painter.  Double-click/place and Drag/Drop functionality will work as it does currently.

The option to open a screen as you would see it in Data Entry.  From this screen, you will be able to drag and drop the fields you need to map as well as add filters.

Quick filters: these will be pre-defined common filters for specific data screens. For example: Address Primary Office, or Active Insurance.  Select the filter you need from the list and the standard filter fields will be filled in for you.  These filters will also be available when mapping from the popup screen.

We are also simplifying the Organization/Application Relationship by converting the separate tabs to a single tree-view.  This will simplify the interface, as well as reduce some of the extra clicks when looking for an application.

If you have any further suggestions, or if you would like to see a prototype when it is available, let us know.