We pass the note to the record. We do not keep it.
dr connect sits between your ambient scribe and your record system. The clinician reviews the note and sends it. We hold the sign-in and licence details we need to run the service, and nothing clinical at rest.
How data moves
Four steps, and the clinician is in control of every write.
The clinician records in the scribe. The scribe produces the note and holds it under its own retention and agreements.
When the clinician opens the note, we fetch it from the scribe and show it, unchanged, for the length of that review.
We never edit clinical content. Corrections are made in the scribe. Nothing is written to the record without the clinician pressing send.
The note goes to the record system through its own import mechanism. The record system is the permanent record.
What we hold
Plain answers, by type of data.
| Data | Held by dr connect? | How long |
|---|---|---|
| Note text, transcript, audio | No. Shown in memory during review only. | Length of the review session |
| Patient name, number, date of birth | No. Not stored at rest. | Length of the review session |
| Opaque references that let us re-fetch a note | Yes. They carry no patient data. | Life of the subscription; erased within 30 days after it ends |
| Clinician work email, role, organisation, site, licence | Yes, to sign you in and check your licence. | Life of the subscription; erased within 30 days after it ends |
| Technical events (versions, errors, reachability) | Yes. Fixed codes only, no free text, no clinical content. Your administrator can switch it off. | 90 days |
| Status page subscriptions (your e-mail address, language, regions chosen) | Only if you subscribe to status e-mails. Held in the EU, apart from the platform, and not linked to your organisation. | Until you unsubscribe; unconfirmed sign-ups 7 days |
| Recording consent records | Yes, if your organisation turns the consent step on. Clinician, time and consultation key only. | The retention period your organisation sets; it is your evidence |
A note that is not reviewed within the scribe's own retention window cannot be recovered through dr connect. That is deliberate: we chose not to become a second store of clinical data.
Where it runs
Our own cloud environment, kept separate from any other organisation's. Each organisation is served from one regional deployment (regions listed below) and its data is processed only there. Traffic enters through a web application firewall; data stores have no public address. Credentials we must keep are encrypted with a key per organisation, held in a vault. Access is by individual sign-in with licence checks every few minutes, so a removed user loses access quickly. Desktop software is code-signed.
Your clinicians stay in control
Optional recording-consent step, automatic screen lock after inactivity, and a clear send-to-record step on every note. Your administrator sets these per organisation.
Sub-processors
Named here because the law asks us to. Your ambient scribe and record system are chosen and contracted by you, so their terms, retention and regions are theirs to state. Your administrator sees your own chain in the console, with a link to each one's own information.
| Provider | Purpose | Location | Clinical data? |
|---|---|---|---|
| Microsoft | Cloud hosting, sign-in, transactional e-mail from the console and the status page | Your region (below) | In memory during review only |
| Cloudflare | Domain name service only; no traffic passes through it | Global name servers | No |
Regions
Generated from the regional deployments that are live, so a new region and its sign-in appear here when it opens. Your organisation's data is processed only in its region. Administrators see their organisation's own data flow, sub-processors and agreement in the console for that region.
| Region | Hosted in | Status | Console |
|---|---|---|---|
| EU | Germany | Live | dcc-eu.dr-connect.it |
Security layers
Documents
Roles, purposes, rights OpenTerms of service
Including the end-user terms On request + Sign inData processing agreement
Standard terms on request. Your signed copy is in the console. On request · NDASecurity pack
Infrastructure diagrams and full questionnaire answers, under a confidentiality agreement.
Compliance status
dr connect holds no certification of its own yet; the cloud platform's certifications cover the infrastructure layer. We list only what is real, with dates, as it is achieved. Our questionnaire answers are in the security pack, available under NDA.
Service status and contact
Live status with up to 90 days of history: status page. Security questions or a vulnerability to report: security@dr-connect.it.