Before anything is installed
Agreements signed, the audit listener details supplied by your integration team, firewall rules for outbound connections, and the department and administrators chosen.
Pilot programme
Four weeks, one department, real clinicians.
We install inside your network, enrol a pilot group on the browser extension, connect the audit path to your integration engine or FHIR store, and hand you the evidence at the end. You keep the audit log either way.
How the four weeks run
Week one: deploy
Tavrik installed in your network, your identity provider connected, the audit path proven end to end with a test event your integration engine receives.
Week two: pilot
The pilot group enrolled, real work through real tools, operators watching what is replaced and what is blocked, compliance reading the evidence as it arrives.
Weeks three and four: tune, then decide
Policy adjusted to what the department actually does; then a steady state you can extend to the next department or stop, with the record intact.
The plan is public and written for the people who will run it. Onboarding a department →
What you need to have ready
- A Business Associate Agreement, and a data processing agreement where your jurisdiction requires one; Tavrik Pty Ltd signs as the service provider and your hospital remains the controller.
- The listener details for the audit path: your integration engine's MLLP host and port, or your FHIR audit endpoint, or both. Tavrik connects outbound to these.
- The certificate authority bundle Tavrik validates your integration engine against; hospital engines usually sit behind an internal authority.
- One department, and the people who will administer Tavrik for it.
Talk to us
Tell us where AI is showing up in your hospital and what would need to be true before clinicians can use it. You will hear back from the people who built Tavrik.