Patient notes and claim narratives.
Not something to type into a shared chatbot.
Private LLM hosting on a dedicated machine in EU-Central, for dental practices drafting patient note summaries, insurance claim narratives, or appointment reminders on a machine assigned to your practice alone.
Not legal or compliance advice. This page describes GPUwerk's infrastructure and contractual commitments. It is not an opinion on your obligations as a healthcare provider, and it is not a claim of any specific certification on GPUwerk's behalf. Check with your own compliance advisor before deciding what can run where. See also private LLM hosting for healthcare for the broader provider setting, and private LLM hosting for insurance for the claims side.
Where an LLM fits into a dental practice's front and back office
This is about the administrative and documentation side of running a practice, not diagnosis or treatment planning.
Patient note summarization
Turning a dictated chairside note into a clean chart entry, or summarizing a patient's treatment history before a follow-up visit. That note carries a patient's name, condition, and treatment detail, exactly the kind of record most practices would rather not send to a shared vendor's servers.
Insurance claim narrative drafting
Drafting the narrative section of a claim, explaining medical necessity for a procedure in the language a payer expects, from the treatment notes already on file. The claim itself names the patient and describes their condition in detail. See the private AI insurance claims processing guide →
Appointment reminder drafting
Generating the text for recall reminders, post-procedure follow-up messages, or rescheduling notices in a practice's own voice, without a front-desk team retyping the same message by hand for every patient list.
On certifications and compliance frameworks
GPUwerk has not published HIPAA, ISO 27001, SOC 2, or any other formal certification, and this page makes no claim that hosting on GPUwerk satisfies any specific healthcare regulation. What GPUwerk provides is a dedicated single-tenant machine, a published GDPR Article 28 DPA with no sub-processors for instance workloads, and a documented answer to who can reach the machine and what happens to data on termination. If your compliance program requires a specific framework, that gives your practice's advisor a concrete starting point to assess against your own requirements, not a substitute for the assessment itself.
What's actually in the contract
For your practice manager or IT contact to review directly.
| Question | Answer |
|---|---|
| Where does it run? | EU-Central, on a dedicated single-tenant machine assigned to your practice |
| Who operates it? | PRINT IT! SE, a Societas Europaea registered in Prague, Czech Republic. No US parent entity. |
| Who can reach the instance? | Through the instance itself, only holders of your SSH keys; password login is disabled fleet-wide. GPUwerk keeps infrastructure administrator access to the underlying machine, as on any hosted service, and under the DPA does not use it on your content except at your request for support or where a legal obligation requires it. |
| Does GPUwerk see patient data? | No. We host the hardware and, under the DPA, do not access, read, copy, index or analyse workload content. |
| Sub-processors for the workload? | None, listed at /legal/sub-processors |
| DPA (GDPR Art. 28)? | Published at /legal/dpa, no charge |
| Certifications? | None published (no HIPAA, ISO 27001, or SOC 2 claimed). Assess against your own compliance requirements. |
| Data on termination? | Container and workspace volume deleted from the node, then the node is sanitised before reassignment. Filesystem deletion, not a cryptographic erase; export what you need before terminating, since it isn't reversible. |
| Pricing | Spark-1x from $0.79/hour on demand, billed per minute; Spark-2x from $1.79/hour. A customer-requested stop holds the reservation at 75% of the running rate. See /pricing for full detail. |
Questions we get from dental practices
Is it safe to put patient notes into an LLM?
That depends on where the model runs and who can reach it, not the model itself. On a GPUwerk dedicated instance in EU-Central, the machine is assigned to your practice alone and reachable only through your SSH keys; GPUwerk does not access, read, copy, index or analyse what runs on it except at your request for support or where a legal obligation requires it. Whether a specific use of patient data meets your own regulatory obligations is for your practice's compliance advisor to confirm.
Is GPUwerk HIPAA certified?
GPUwerk has not published HIPAA, ISO 27001, or similar certifications. If your compliance program requires a certified provider or a specific control framework, a dedicated single-tenant instance with a published DPA and no sub-processors gives you a documented starting point to assess against your own requirements, not a substitute for that assessment.
Do you sign a DPA covering patient data?
Yes, a standard GDPR Article 28 DPA is published at /legal/dpa at no charge, and there are no sub-processors for instance workloads.
Does GPUwerk train on our patient records?
No. GPUwerk runs infrastructure, not models. There is nothing for GPUwerk to train on, since we do not access instance content except as described in the DPA.
Related reading
Private LLM hosting for healthcare · Private LLM hosting for insurance · Private LLM hosting for veterinary practices
Related pages
Keep patient records off someone else's servers.
Talk to the people who run the racks, or start with a pilot and a practical rollout plan.
Talk to us Deploy an instance