Introduction to TAFi

Last updated [Full Date & Time (GMT)]

TAFi is a software platform that enables applications and analytics in the healthcare setting using secure data exchange, blending, and storage.  It’s not typical healthcare middleware, so think of it as an integration engine + data warehouse + API. Data enters TAFi like it would with an integration engine first, then after governance/normalization of inbound data it’s able to be blended with other sources, stored (like a data warehouse), and if necessary, sent outbound to an app or as analysis.  This probably seems like alot, and that’s because it is. The TAFi Platform, in real-time, does the work of a traditional integration engine, data warehouse, and API service combined. Pretty neat right?

Is TAFi in the cloud, or does it install on-premise?

Great question!  It can be either.  TAFi has a multi-tenant, multi-region cloud deployment built out on Amazon Web Services (AWS).  We use AWS because of their strong portfolio of technologies, some of which we use, other that we don’t, that are HIPAA-compliant, and very stable.  Additionally, they tend be better priced, so it allow us to pass those saving on to your organization.

In scenarios where AWS does not meet your organization or your client’s security profile.  TAFi is able to deploy in virtually any data center so long as it meets the requirements necessary for us (and you) to maintain our compliance to HIPAA.

Quick Start Guide

Last updated [Full Date & Time (GMT)]


This guide will walk you through the quickest way to get rolling with testing out your app against TAFi’s sandbox.



This is where we need the details on how to authenticate against our sandbox/API


Source & Destination Planning

This is where we include the instructions on how to configure the source and destination routing


Testing with the TAFi API

Include instructions, with maybe a very simple example, on how to execute a test to the API. Include a table of the responses that could come back, and what they all mean, with some possible troubleshooting steps if the response is not favorable.