Third Party Software Integrations

This article provides detailed information relating to which third party systems SupportAbility integrates with for transmitting data between systems. 

SupportAbility provides flat file exports for integration with the following third-party systems: 

  • Finance
  • Award Interpretation and/or Payroll
  • myplace provider portal

API integration is not available with these systems as yet for the reasons outlined below. 

Audience: Authorised Representatives, Finance Team, IT Specialist

Summary

The following list summarises the content within this article. Click on the links below to take you to the relevant sections:

Integration options for transmitting data between systems

Whilst there are a number of methodologies to transmit data between software packages as a means of integration, namely Flat File Exports (CSV/Tab Delimited), API Integration and Direct Database transfer as outlined below; SupportAbility currently only integrates with the aforementioned third party systems, by exporting Flat File data which those systems then import and interpret. 

Integration Method Description Pros Cons Best Suited For Factors
Flat File Exports (CSV / Tab-Delimited)
Flat files are simple
text files such as
Comma Separated
Value (CSV) files or
Tab Delimited files
that are exported
from the sending
system (usually to
a Staff Member's
computer) and then
uploaded to the
receiving system. 
The CSV download in SupportAbility is delivered under full RSA 2,048 bit banking-grade encryption
  • Fast to build
  • Cheap to build
  • Easy and fast to modify
  • More control to review data before uploading and then only upload when ready
  • Able to make adjustments directly if there are any issues without the need to wait for developers to scope, estimate, build, test and deliver a solution which could take weeks
  • Manual download and upload
  • An export data file can potentially manipulate data between the export and import processes
  • Rapid solution provisioning
  • Proof of concept or prototyping
  • Integrations when more control is required
  • Organisations that do not have advanced technical staff
  • Situations, where at least one of the software systems is rapidly evolving as the cost and speed of making adjustments, is more forgiving
 Costs:
LOW

Time:
LOW

Automated:
NO

Control:
HIGH

Risk:
LOW
API Integration Application Programming
Interfaces (APIs) allow
the sending software to
trigger pre-defined actions
and/or manipulate data
in the receiving software
within a strict set of
guidelines.  API integrations
are generally used to
automate transactions
between systems.  API
Integration requires
significant development
resources from the Sending
software company and
also from the Receiving
company if the API end
points (predefined actions)
do not yet exist and are
being built as part of the
integration process.
  • Automated
  • No room for data manipulation
  • More efficient after completion
  • Less control to review data before uploading and then only upload when ready
  • Slow and expensive to build
  • Slow and expensive to modify
  • Prone to breaking if systems are changing
  • If there are any issues, developers need to scope, estimate, build, test and deliver a solution which could take weeks
  • Both systems are very mature software systems that do not change much
  • Organisations that have highly technical staff
  • Automation is required
 Costs: 
LOW 

Time: 
LOW

Automated: 
NO

Control: 
HIGH

Risk: 
LOW
Direct Database Access This is where the sending application directly manipulates data in the database of the receiving system.
  • Automat-able
  • Faster and cheaper to build than API Integrations
  • VERY DANGEROUS as the sending system does not have the required domain knowledge to edit the data directly
  • Both systems are very mature software systems that do not change much
  • Organisations that do not have software engineers on staff
  • Integrations when automation is required
  • Situations, where at least one of the software systems is rapidly evolving as the cost and speed of making adjustments, is more forgiving
  • The receiving system has excellent domain knowledge of the receiving systems
 Costs: 
MEDIUM 

Time: 
MEDIUM

Automated: 
YES

Control: 
LOW

Risk: 
HIGH  

Return to Summary

Why doesn't SupportAbility work with APIs yet?

SupportAbility is a reasonably young product that is trying to support an industry undergoing serious foundational change as the National Disability Insurance Scheme (NDIS) rolls out across the country and is being constantly monitored and adjusted.  

We are continually enhancing SupportAbility to meet the ever-changing needs of this industry in flux. We currently release approximately 20 new versions of SupportAbility each year in an effort to give service providers the tools they need to manage their obligations under the NDIS.  However, this high rate of change also means that it is too early for SupportAbility to build API integrations with other systems.  API integrations are very expensive and time-consuming to build, and they are very expensive and time-consuming to modify in situations where the software systems are changing.

We are excited at the prospect of building a SupportAbility API in the future, and also integrating with third-party APIs, but we need the NDIS compliance requirements and the SupportAbility product to mature and settle before that can happen.

Return to Summary

Are there any other options available, apart from APIs?

If your organisation truly requires tighter, more automated integration, we do offer a SupportAbility Data Replica Subscription which if this subscription is taken out gives your organisation direct access to the raw SQL data that underpins your SupportAbility installation. Using this you can employ technical resources directly to build the integrations you require.

Return to Summary

Still need help? Contact Us Contact Us

Related Articles