The federal frame
HIPAA's Privacy and Breach Notification Rules apply to covered entities. The system's access rules and data path are documented for review against them.
Healthcare operations / private assistant / the United States
Private AI for clinics and HMOs in the US, built around the HIPAA Privacy Rule.
Private AI for US clinics and HMOs: approved policies, staff procedures, and administrative documents made searchable inside the clinic's own environment. Clinics are typically HIPAA covered entities, and the Privacy and Breach Notification Rules set the expectations — the deployment is designed for review against them, with a business associate agreement when one applies.
One workflow from $3,500 / ₦2.5mApproved-corpus accessPermission boundaries2 to 3 weeks
Pattern demonstration / not clinical advice
No clinical decisionsDesigned for review against state privacy laws and professional confidentiality rulesApproved-corpus accessFull handover
Why it matters here
The US health-data frame comes from HIPAA and the states.
HIPAA's rules apply to covered entities, and state laws add their own layer. The deployment documents one path for all of them.
Named processors
Where a vendor touches protected health information, a business associate agreement applies. Every processor is named in the handover.
The patchwork
State laws add their own health-privacy rules. The documented data path is reviewable against whichever apply.
What we set up
A healthcare page should say what it will not do.
Not every patient file
A defined corpus and access model. Sensitive records require secure transfer, purpose, permissions, and review before anything is indexed.
Disclosed provider path
API-backed, regional, private, and local setups have different routes for prompts, retrieval, logs, and support. The route is written down.
Human authority stays
The system assists an approved workflow. A clinician or qualified administrator owns the actual decision.
A first project
One administrative question.
Policy and procedure search
Approved policies, staff procedures, and service information searchable through a private web app. One training session, a runbook, and credential handover.
The accounts and the keys
Cloud, model provider, and storage accounts stay in the clinic's name. You receive the runbook, credentials, and test record.
How it lands
Discovery to handover in one flow.
Discovery
The questions staff answer most and the approved documents that hold the answers.
Boundary
What may be searched and drafted, and what must remain with a qualified clinical, legal, or operational owner.
Build and test
Tests on real staff questions, with access checks, unsupported questions, and failure cases verified.
Handover
Training, an admin runbook, and all accounts transferred to the clinic.
HIPAA review, named processors, and state rules. One documented data path serves all three.
Why trust Pristine3D?
We build and operate production software.
Pristine3D Ltd builds and operates live digital products, and we run private AI workflows internally as part of our own operations. We scope around your real workflow: the documents you own, the questions your team asks, and the access boundary you approve. Based in Lagos, Nigeria, we work remotely with clients worldwide.
We already run live products
Based in Lagos, Nigeria, Pristine3D currently builds and operates smartcards.ng, venu.ng, photoshoot.ng, and ugc.ng in production.
We start with the actual workflow
One input, one output, one test set, and one person who owns the result. We scope a real workflow instead of a transformation programme.
The boundary stays visible
Cloud, model, storage, and messaging accounts stay in your name. The chosen data path, access rules, test record, documentation, and training are part of the agreed scope.
Pricing / fixed scope
Know the starting numbers before you ask.
The final quote follows the workflow. Infrastructure and model bills stay on your accounts.
One Workflow
Starting from$3,500 / ₦2.5m
2 to 3 weeksOne workflow for a small team, with training and handover.
See the one-workflow packageFirm-wide
Starting from$7,500 / ₦8m
4 to 6 weeksMultiple sources, roles, integrations, and admin handover.
See the deploymentAnnual support
Starting from$3,000 / ₦1.5m
per yearStandard care for one delivered workflow. Optional. Larger deployments and active monitoring are separately scoped.
See supportArchitecture review from $500. Standard annual support is $3,000 / ₦1.5m per year for one delivered workflow. New workflows, integrations, active monitoring, and infrastructure are separately scoped; infrastructure, model, storage, and messaging bills stay on client accounts. Full pricing and what changes the quote
Straight answers
Common questions.
Where would the clinic's documents be hosted?
Hosting in a US region such as us-east-1 (Virginia) or us-west-2 (Oregon) is the default, with on-prem for stricter requirements.
How does HIPAA fit?
The obligations belong to the clinic. The system supports them with controlled access, named processors, and a documented data path designed for review against the Privacy and Breach Notification Rules.
Can it work with patient information?
Only after the purpose, access model, secure transfer, provider path, retention, and professional review requirements are agreed with the clinic — including the business associate relationship where one applies.
Do invoices come in US dollars?
Yes, from $3,500 for a first workflow, with the naira floor unchanged.
Own your knowledge base
The model is not the product. The knowledge base is.
Documents, the retrieval index, access rules, and the workflows built around them are the asset, and they compound. We deploy so the knowledge base stays yours: on your accounts, in the environment you choose, under access rules your team defines. The model behind the answers is a connector, so the knowledge base moves with you, not with a vendor.
Your corpus, your index
The document store, metadata, and retrieval setup live on accounts you own. No vendor holds the corpus.
Models are swappable parts
Change the model provider, move regions, or go local without rebuilding the knowledge base or the workflow.
The knowledge base is the alpha
Every improvement to the corpus improves the answers, and the improvement stays with you, not with a vendor.
Keep exploring
Related setups.
Start with the approved information
Which healthcare question keeps returning?
Tell us the user, source, sensitivity, output, and human owner. We will help separate a safe workflow from a clinical decision.