Last updated October 2026
Healthcare organizations ask us the same questions before a first project: what data do you need, where does it go, and how is AI used? Here are our answers, in plain language.
No PHI, by design
Our process is built so that no protected health information is ever needed or accepted. We build training from your policies, SOPs, slide decks, and de-identified or fictional examples. Every patient or client in a scenario is a fictional composite, like “Mr. Davis” in our demo.
- We ask you not to send PHI, and our forms say so.
- If PHI reaches us by mistake, we delete it, tell you, and ask for a de-identified version.
- Because standard projects never involve PHI, we design our work so that no PHI flows to us or to our production tools.
How we use AI tools
We use AI tools as production equipment, with a nurse in charge of the content:
- AI presenter video (HeyGen): we send the approved script text to generate the presenter’s video and voice. Only the approved script goes in, never PHI or confidential data.
- Drafting help: AI writing tools may help draft or edit scripts and questions from the source policy you provide. Every line is reviewed by Rob Sieck, RN, and then by your named reviewer.
- Captions and transcripts: may be generated with speech-to-text tools, then checked against the approved script.
Nothing is published that a person hasn’t reviewed and you haven’t approved.
AI presenter disclosure
Presenters are AI-generated video, and we disclose that clearly to clients. We recommend, and can include, an on-screen disclosure for learners. Our own founder video is presented by Rob’s AI avatar, created from his own likeness and voice with his consent.
Presenter consent
We use stock AI presenters licensed through our tools, or a custom avatar of a real person. A custom avatar of one of your leaders is created only with that person’s documented consent, and only for the projects they approve. They can ask for it to be retired at any time.
You own the final files
Your organization owns the final delivered files (the web module, MP4, captions, and checklists) and can use them internally without ongoing fees. Our underlying tools, templates, and methods remain ours, and third-party assets such as stock presenters stay subject to their licenses.
Where data is stored
- Website forms: Netlify Forms, part of our website host.
- Email and project files: our business email and cloud storage accounts, limited to the people working on your project.
- Presenter video generation: HeyGen, which processes the approved script.
- Calls: Calendly for scheduling and Google Meet for calls. We don’t record calls without asking first.
After delivery, we keep project files so we can make future revisions, unless you ask us to delete them. Just email rob@tpmlearningstudio.com.
What we don’t claim
We don’t claim certifications or attestations we don’t hold. Our content is designed to support your compliance program, and your organization reviews and approves all content. See also our Privacy Notice and Accessibility statement.