License your health data for research and AI, with proof built in.
Prepared under a BAA, protected in your environment, documented for an independent qualified expert and for the recipient’s diligence team.
The most valuable signal sits with the most identifiers.
AI developers and research teams want real clinical data. Health systems, health plans and data networks hold it, in records, notes and documents that can’t be shared as they are. Strip them too hard and the data loses its value. Strip them too lightly and you carry the risk.
HIPAA allows de-identification by expert determination: a qualified expert finds that the risk is very small that the data could identify someone, and documents the methods and results (HHS). A fully described dataset is what makes a sound determination possible.
Four steps to a licensed release
- 01Sign a BAA and agree the release.
- 02The Tidegate engine protects the data in your environment, in Expert Determination mode.
- 03An independent qualified expert reviews the release with its risk summary.
- 04You license it to the recipient, with the release pack.
What you get
- A de-identified dataset with realistic, consistent replacements and one date offset per person
- Entities, condition status and the codes already in your data, extracted and labeled. On the roadmap: relations and social determinants.
- Synthetic data for development and testing, released only after memorization tests, with a synthetic data report
- Holder-issued, purpose-scoped pseudonyms, linked within your data. On the roadmap: linkage across organizations.
- The release pack, ready for the recipient’s diligence team
What a lab’s diligence team checks
What ships with a release
Questions
- Do patients need to be notified or asked?
- It depends on the HIPAA pathway and on state law. Your counsel decides; the release pack records what was done.
- Does Tidegate buy, sell or broker the data?
- Never. You contract directly with the recipient.
- Who makes the determination?
- An independent qualified expert you engage. We prepare the release and introduce you to experts.
- How long to a first release?
- It starts with an evaluation on your own records; see Start with an 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. You get release-pack documents 01 to 06 on your own records, then a written proposal for your first release, or nothing further.