The trust layer for health data · Tidegate
The trust layer for health data

Get your health data ready for research and AI, without it leaving your control.

Health systems, health plans, data networks and public programs hold the records researchers and AI developers need. The Tidegate engine runs inside your environment to find every identifier, protect it under the HIPAA pathway you choose and label every field with the rules that govern it, so your data can move with proof.

Evaluations are booking now for spring 2027.

FIELDLABELED
member_dob●●/●●/19●●
WHAT IT ISDate of birth PHI · quasi-identifier
RULESHIPAASTATE LAW
MAY BE USEDRESEARCH: YESMODEL TRAINING: NO
STATUSMasked · Expert Determination mode
Illustrative. Fictional field.

Meaning. Permission. Proof.

  1. 01 Meaning Know what your data holds. Every identifier and clinical fact found and labeled, with condition status and the codes already in your records. Discover. Find identifiers and clinical detail in tables, notes and documents.
  2. 02 Permission Choose how it moves. Safe Harbor or Expert Determination, permitted uses on every field, and a qualified expert or your caseworker makes the call. Protect. Protect identifiers in your environment, under the HIPAA pathway you choose.Label. Tag every field with what it is, the rules that govern it and its permitted use.
  3. 03 Proof Show your work. Every release ships with its labels, checklist, risk summary and the documents a recipient’s diligence team asks for. Link. Connect each person’s records within your data, with match quality reported.

Researchers and AI developers are asking for clinical data faster than privacy teams can review it by hand.

Labels are machine-readable, so your query layer and pipelines can enforce them.

The problem

The most valuable part of the record is the hardest to use safely.

Clinical notes, case notes, faxed letters and scanned documents hold the detail that decides a study, a data license or a coverage decision, and the identifiers with it. So organizations either lock that data away and lose its value, or release it and carry risk nobody has measured.

{{ p.who }} {{ p.stat }}–{{ p.stat2 }}

{{ p.text }} ({{ p.credit }}).

Using that data safely starts with knowing exactly what is in it.

See the engine
Markets

One engine. Four markets.

Each market loses something different when its notes and documents go unused. One engine finds what they hold and keeps it governed in your environment.

{{ p.eyebrow }}

{{ p.title }}

{{ p.body }}

{{ p.link }}
Use cases

What teams do once they know what their data holds.

Discovery comes first. These are the outcomes the Tidegate engine supports from there, each one running in a cloud account you control, so identifiers and record-level data stay in your environment.

02

AI-ready data for model development

Prepare clinical and claims data for training, fine-tuning and evaluating internal or partner models. Synthetic data for development and testing, released only after memorization tests, with a synthetic data report.

FORData science and ML teams, and life sciences R&D groups building or evaluating models
03

Data commercialization and research

Prepare EHR data and clinical notes for AI developers and research partners. The Tidegate engine transforms them in your environment, deployed with Tidegate Forward Deployed Engineers under a BAA whenever they access PHI, and an independent, qualified expert you engage reviews the release.

FORHealth systems, health plans and data holders with the rights to license: labs, pharmacy and PBM data, clearinghouses, specialty networks, digital health, health data networks
04

Sensitive data discovery and governance

Inventory and classify sensitive attributes across structured and unstructured data, grounded in Tidegate’s data attribute ontology, for compliance, audit and risk reduction.

FORPrivacy, compliance and data governance teams, including state Medicaid agencies and other public payers
05

Linkage and interoperability readiness

The next step once data is clean and classified: connect each person’s records within your data, with match quality reported, and export them to OMOP, CSV or Parquet with their labels attached. From v1.1: FHIR with Provenance.

FORTeams joining claims, EHR, lab and note data, or preparing it for exchange with partners
See all use cases
Fits your stack

Works inside the systems you already use.

Data networks, eligibility systems and data platforms run the engine where the records already are.

Show the example for
{{ s.title }} {{ s.ref }} {{ s.where }} · ILLUSTRATIVE
{{ s.railLabel }}
{{ r.label }} {{ r.flag }}
{{ s.docHead }}

{{ sg.t }}

{{ lg.t }}
VERDICTS
{{ v.label }} {{ v.chip }}
{{ s.toast }}
Reads FHIR R4 HL7 v2 C-CDA X12 837 and 835 NCPDP OMOP Clinical and case notes Documents with a text layer
All formats

Run a network, token service, eligibility system or data platform? Build Tidegate into it.

Become a partner
Trust

Your data stays in your environment.

The engine acts as a neutral trust layer between the suppliers, users and regulators of health data. These commitments are what let it.

Models run locallyDiscovery, protection and linking run in a cloud account you control. From v1.1: on premises and air-gapped installs.
Health information stays putIdentifiers and record-level data stay in your environment. Only output you approve leaves it. If you share review corrections, only the decision travels.
Nothing phones homeNo calls to outside AI services and no telemetry. Signed updates are pulled only when you choose. From v1.1: signed offline updates.
NeutralTidegate never buys, sells, holds or brokers data, and never competes with the suppliers whose records it governs.
Open, not locked inWorks with the tokens you already have, and issues holder-issued, purpose-scoped pseudonyms, so you are not tied to one vendor.
Machine-readableLabels are machine-readable, so your query layer and pipelines can enforce them. On the roadmap: checking each data request against its labels as it runs.
Evaluation

Start with an evaluation

We run the Tidegate engine on a sample you choose, scoped in writing, in a cloud account you control, for a fixed period agreed in writing.

Evaluations are booking now for spring 2027.

Agreements
An evaluation agreement and NDA, and a BAA whenever Tidegate engineers access PHI.
What you provide
A cloud account you control, a technical contact and a privacy reviewer.
What you get back
Release-pack documents 01 to 06 on your own records.
What happens next
A written proposal for your first release, or nothing further. Your data never leaves your environment either way.
Public agencies
Agencies start with a briefing on fictional case files, then an evaluation under your agreements.
Request an evaluation