Pilot plan
A pilot you can say yes to.
A time-boxed evaluation in your own environment, on invented patients, with questions agreed up front and a clean way out.
What it is
Small, honest and reversible.
It is an evaluation
Your people try ZYVORA against your own workflows and rules, on synthetic data, and judge whether it fits.
It is not a go-live
ZYVORA is not certified and has only held invented data. A pilot never uses real patient records.
It runs on your side
In your own environment, with your identity provider. Remove it with one command; the containers and their data go with it.
The plan
Nine weeks, five steps.
Dates are agreed per pilot. The shape stays the same.
Week 0: agree the questions
Together we write down three to five questions the pilot must answer, who decides, and what counts as a yes. Nothing starts before this is written.
Weeks 1 to 2: install and walk through
IT installs ZYVORA in your own environment with invented patients. Each role (doctor, nurse, pharmacist, front desk, administrator) walks its own day.
Weeks 3 to 4: set it to your rules
Your clinicians and managers enter what ZYVORA deliberately does not ship: note templates, programme ranges, lab and imaging targets, tariffs, payment terms, retention rules.
Weeks 5 to 8: rehearse your workflows
Staff replay your real workflows as invented scenarios. IT rehearses each connection against a test system, and runs backup, restore and upgrade.
Week 9: review and decide
We compare what happened with the questions from week 0, list every gap honestly, and you decide: stop, extend, or plan the next stage.
Who does what
Clear on both sides.
What we provide
The software and installer, a named contact, a walkthrough for every role, help configuring your rules, a weekly check-in, and an honest gap list at the end.
What you provide
A sponsor who can say yes, one or two clinical leads, someone from IT, a place to run it, and the time of the staff who will try it.
What we both write down
The questions to answer, the success measures, who decides, and the end date, in one page before week 1.
Questions a pilot can answer
Examples to start from.
Does it match our wards?
Does discharge planning, handover or the waiting list work the way our teams actually work?
Can our coders and billers use it?
Do the code catalogue, tariffs, claim files and fee rules fit our payers and our process?
Can IT run it?
Install, upgrade with rollback, backup and restore, sign-in through our identity provider.
Would security approve it?
Does our review accept the controls, and can we live with the published gaps?
Does it speak our language?
Do the right-to-left layout and the draft translations meet our needs, or what must be added?
What is missing?
Which of our must-haves is not built yet, and how far is it from what we need?
Before any real patients
What a pilot does not remove.
Not certified
No certification against HIPAA, GDPR, ISO 27001, SOC 2, IEC 62304, NABH or JCI. A gap list is published.
Work still to do
Clinical validation, the certifications your country requires, an independent security review, load testing and acceptance of each connection against your real systems. The intended-use page lists them.
Price
Agreed per pilot, not guessed.
Pricing has not been decided and nothing on this site is an offer. Tell us the scope you have in mind and we will propose terms in writing, including how the pilot can end.
Ready to define your pilot questions?
Synthetic data only. Not a certified medical product. No price is an offer until we agree one together.