- Number Loader
- Gazetteer Loader
- Single Sign On via SAML
Every integration is different, but Liquidlogic has evolved a methodology which ensures consistency and success, regardless of the third party systems.
Our starting point is an understanding of the outcomes and benefits to users. Our Integration Consultant will meet with the customer and the third party system provider to understand what the integration is going to achieve – for service users and for councils.
Liquidlogic documents this discussion in a functional specification which is agreed with all parties before we move on to the technical aspects of the integration. It’s important to note that we always start with the ‘why’, ‘what’ and ‘who’– why are we integrating, what will the integration achieve, who benefits?
The vast majority of integrations use Liquidlogic APIs. Where there is a specific requirement which isn’t met by the current APIs, we will typically upgrade the API specification itself so that future interface work also benefits from the enhancements. This is simply a facet of our continuous improvement mindset. Our consultant will share a detailed integration specification with all parties; this includes granular detail at message level, and acts as the blueprint for the interface and a reference document for any future enhancements.
Openness is a key attribute of Liquidlogic and has been from the start. Some suppliers try to ‘lock’ their customers in to a suite of products. Our approach is the opposite – every customer has a different blend of systems, we see it as our job to help you to collaborate effectively for the benefit of your service users.
Ultimately, a Liquidlogic system is there to help professionals to work with the most vulnerable in society. We want to help in any way we can.