Delivery · Tidegate
Forward Deployed Engineers

The Tidegate engine, delivered by people who have done it before.

Not every organization has the engineers, the bandwidth, or the privacy expertise to stand up a new trust layer. Tidegate Forward Deployed Engineers close that gap with two services: engineers who deploy the Tidegate engine inside your environment, and, when your use case calls for it, introductions to independent, qualified experts who review what the engine has prepared.

01

Forward Deployed Engineers

Our engineers, inside your environment, for a scoped engagement.

Tidegate Forward Deployed Engineers work directly in a cloud account you control, under your access controls. They deploy and operate the Tidegate engine, connect it to your pipelines, connect your data sources, and tune data discovery to your records, from structured claims to unstructured clinical notes and embedded documents. Whenever they access PHI, a Business Associate Agreement is in place first, and they use only the access your team grants.

The Tidegate engine is designed to run inside data platforms, network query layers and state eligibility and case management systems, working alongside your systems integrator where you have one.

What they deliver

05 PHASES
  1. SCOPE
    • Scoping of use case, data sources and success criteria
  2. DEPLOY
    • Container deployment or SDK integration in your environment
    • Source connections and data discovery mapped to the Tidegate ontology
  3. CONFIGURE
    • De-identification in Safe Harbor or Expert Determination mode, and synthetic data released only after memorization tests, configured to your use case
    • Permitted-use labels configured with your privacy team
    • Entity linking and delivery into your formats and systems
  4. VALIDATE
    • Validation on your records, with thresholds and review queues set with your team
    • Full documentation of findings and transformations
  5. HAND OVER
    • Hands-on knowledge transfer to your team
    • Runbooks and monitoring for ongoing operation
OUTCOMEThe Tidegate engine running in your environment, with every finding and transformation documented.
WHEN YOUR USE CASE CALLS FOR EXPERT DETERMINATION
02

Independent, qualified experts

Independent experts. Prepared data. One handoff.

Under HIPAA, expert determination is made by a qualified expert who applies accepted statistical and scientific methods. Tidegate never makes or owns the determination. We introduce you to independent, qualified experts. You engage the expert, and we hand off a dataset that is ready for their review, with discovery findings, risk documentation, and transformation records already assembled.

What you get

  • Introductions to qualified providers matched to your data type and use case
  • Datasets and documentation prepared to their review standards
  • Coordinated remediation if the expert requests changes
  • Support for re-determination as your data or use case evolves
OUTCOMEA shorter, more predictable path from raw data to a defensible determination.
Ways to work

Deployed and operated with you.

Tidegate Forward Deployed Engineers deploy and operate the engine in a cloud account you control, under a BAA whenever they access PHI. Packaged installs from v1.1.

01In your cloud accountThe engine runs in a cloud account you control, under your keys and access controls. From v1.1: on premises and air-gapped installs.
02Our engineers stand it upForward Deployed Engineers scope, deploy, configure and validate on your records, then hand over with runbooks and monitoring.
03Alongside your integratorWhere a systems integrator already runs your platform or eligibility system, we work inside their delivery plan and contract.
By market

What a deployment looks like for you

The engine is the same everywhere. Where it sits, and who we work with, depends on your market.

HEALTH SYSTEMS AND PLANS

Next to your records and AI tools

Where it runsIn a cloud account you control, in front of approved AI tools and next to your warehouses and note stores.
Who you work withYour data, AI governance, privacy and security teams, and for plans, your care management and prior authorization teams.
LIFE SCIENCES AND REAL-WORLD EVIDENCE

Inside your data platform

Where it runsAs batch jobs next to your notes and OMOP tables, or inside your real-world data provider’s environment.
Who you work withYour RWE, data science and privacy teams, and your data providers where they host the data.
HEALTH DATA NETWORKS

In your query layer and pipelines

Where it runsAlongside the linkage and tokens you already use, where feeds arrive and where requests are served.
Who you work withYour data engineering, product and privacy teams.
PUBLIC PROGRAMS

Inside your eligibility system

Where it runsAt document intake, as uploads and faxes arrive, and alongside the claims and eligibility records you already hold.
Who you work withYour systems integrator, eligibility policy staff and caseworker leads.
Before we start

What we need from your team

A short list, agreed during scoping, so the first run happens on your records and not on slides.

An environmentA cloud account you control, with access set by your security team. From v1.1: on premises and air-gapped sites.
A sample of your dataRecords, notes and documents that reflect the real mix. The sample stays in your environment.
A privacy leadSomeone who owns permitted use and sets review thresholds with us, and an expert where expert determination applies.
Security and deployment details

Technology that ships with the people to run it.

Tell us where your data sits and what it needs to do. We will walk you through the plan in a briefing.