Health data networks · Tidegate
Health data networks

Know what your notes and documents hold, before they reach partners.

The Tidegate engine discovers and protects the identifiers and clinical facts in your notes and documents, so your data is safer to share and ready for the partnerships you choose. Labels travel with every record and are machine-readable, so your query layer and pipelines can enforce them.

Your network · Partner request REQUEST R-3318
Diagnoses and labsPurpose: model trainingLABELED · PERMITTED USE
One person across 3 feedsLinked within your data, one person IDMATCH 0.94
Substance-use treatment notesOn the roadmap: likely Part 2 content flagged and held for your reviewPART 2 HOLD · ROADMAP
Release logged with labels, a risk summary and a referential integrity report
Illustrative. Fictional request. Solid: available. Outlined: ROADMAP.
SOC 2 Type I and HITRUST e1 in progress · Runs in a cloud account you control · BAA whenever our engineers access PHI · Never buys or sells data
DATA REQUESTS Partners and AI developers now ask for records by category.A contract cannot stop a query. Labels 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.
Path to live

From one feed to every partner

  1. 01BriefWe walk your data and privacy teams through the Tidegate engine on fictional records, share the security packet and map where records enter your network. An evaluation on one of your own feeds follows once your agreements are in place.
  2. 02PilotOne feed or one partner request goes live. Labels travel with each record, and your team reviews what each request receives.
  3. 03Network-wideEvery feed and query path is added under the same labels, with match quality within your data and a risk summary reported each release.
AgreementsWhenever Tidegate engineers access PHI, a Business Associate Agreement is in place first. Labels map to your licenses and data use agreements, and you decide what each partner receives.
What you get

What changes on Monday morning.

For health data networks

Data you can license, share and use with confidence.

TodayNo one knows exactly what the notes and documents in a feed contain. Permitted use lives in contracts, and requests are checked by hand, if at all.
With TidegateYou see what each feed holds, and identifiers are protected before it is licensed. Every field carries machine-readable labels for regime and permitted use, so your query layer and pipelines can enforce them.
Discovery in notes and documentsIdentifiers and clinical facts found in free text, documents with a text layer and embedded documents, then protected. From v1.1: scanned documents.Track: identifiers found outside structured fields
Feeds documented before releaseMatch quality within your data and a re-identification risk summary ship with every release.Track: feeds released with a release pack
Governed downstream sharingLabels stay attached to the extract, so the next party receives the same rules alongside your license terms.Track: downstream releases with labels attached
Machine-readable permitted useLabels are machine-readable, so your query layer and pipelines can enforce them. On the roadmap: checking each request against its labels as it runs, and relatives told apart from the patient.Track: fields released with labels attached
Uses

Where it matters

One pattern: every field carries machine-readable labels, and your query layer and pipelines enforce them.

01Partner data requests The requestA partner asks for “all cardiology records” to train a model What Tidegate doesFields labeled for model training, for your query layer to release. On the roadmap: likely Part 2 notes held for your review Who sees itYour data steward sees the labels on every field released
02Feed check The requestA supplier feed offered for model training What Tidegate doesMatch quality within your data and a risk summary reported with the release Who sees itYour team approves the feed or sends it back
03Downstream sharing The requestA licensed extract shared with a third party What Tidegate doesLabels travel with the extract, so the next party’s systems can enforce them Who sees itYour team approves the release, on the record

Illustrative. Fictional requests.

Principle

Neutral by design

Tidegate never buys, sells, holds or brokers data. We never compete with the suppliers whose records we govern, and we agree up front which accounts we serve together. Tidegate works alongside the linkage and tokens already in your network.

Resolution

The hard cases

THE HARD CASES03 CASES
01A surname that is also a medicationThe name is tagged NAME · PATIENT; the drug in the next line is tagged MEDICATION.NAME · PATIENT · MEDICATION
02An MRN in the header and again in free textBoth are found and get one replacement.MRN
03One person under a maiden and a married name in two feedsLinked within your data at MATCH 0.91, with one person ID.MATCH 0.91
How you get it

Inside your network

Tidegate runs in your environment, next to your query layer and delivery pipelines. Identifiers and record-level data stay there. Only output you approve leaves it.

Need hands-on help? Tidegate Forward Deployed Engineers deploy the engine in your environment, under a BAA whenever they access PHI, and we can introduce you to independent, qualified experts who review licensable data the engine has prepared.

Coverage

What this means for your data

The identifiers that matter most are often the ones nobody expected: a member ID in a free-text note, a device serial number in an attached report. The Tidegate engine finds them in unstructured and embedded content, not just in labeled fields.

What the engine recognizes
Designed to support review under 42 CFR Part 2 holds · ROADMAP State health privacy laws HIPAA Expert Determination
Sample output A structured claim after protection

Questions we hear first

Does one person keep one identity across feeds?
Yes: one replacement identity per person across every feed and release.
How do labels help with exchange obligations?
Labels are machine-readable, so your exchange and query layers can enforce permitted purposes. Tidegate does not decide them.
What do licensees receive?
The release pack. See data commercialization and research.
Technical fitNext to your query layer and pipelines.
MODEBatch per feed and per release; labels your query layer enforces. On the roadmap: checks as each request runs
INPUTSClaims, EHR and lab feeds, notes, existing tokens
DEPLOYYour cloud account or Kubernetes cluster, under your keys
Engine details