您的患者將最敏感的資訊託付給您。我們建立的平台也以同樣的方式對待這些資訊。
Most dental software encrypts your data "in transit and at rest" — which means the disk is encrypted, but anyone with database access sees every patient's name, birth date, and phone number in plain text. We go further: each PHI field is individually encrypted with AES-256-GCM under a key scoped to your practice before it's written. Here's the same patient record, as your team sees it and as it physically exists in our database.
Decrypted on demand, only for authenticated members of your practice.
first_name: null last_name: null date_of_birth: null phone: null email: null encrypted_phi: "eyJlbmNyeXB0ZWQiOnRydWUsImFsZ29yaXRobSI6ImFlcy0yNTYtZ2NtIiwiaXYiOiJJZHRoaExVNlhwU3FaanVSTFdrYkNBPT0iLCJkYXRhIjoiSVdPRW5sQWNrQ3psNVVJdHpvbW12YmkxQnRQOCtUYkhyZ2R1…"
A real row from our database (demo patient). The plaintext columns are null — the record exists only as ciphertext.
八層防禦機制,內建於每份表單、每筆記錄、每個請求中。
每個 PHI 欄位都使用 AES-256-GCM 單獨加密,並配有專屬的單筆記錄資料加密金鑰。即使某一金鑰遭到破解,也只會洩露該筆記錄,而非整個資料庫。
我們運行於具備 SOC 2 Type II 認證的 AWS 平台,提供 99.99% 正常運行時間 SLA。多區域備份搭配加密儲存與自動故障轉移。
即使是 Intake.Dental 管理員也無法存取未加密的患者資料。解密金鑰僅限租戶範圍,且永不記錄。
每個請求 — API、儀表板、表單提交 — 均透過 TLS 1.3 傳輸,強制執行 HSTS 並僅提供 HTTPS。
符合並超越所有 PHI 技術保護措施,並提供免費簽署的 BAA。
聯邦加密標準:256 位元金鑰、GCM 驗證。
基礎設施運行於 AWS 的 SOC 2 Type II 認證基礎上。
Most healthcare software still protects patient data with public-key cryptography that quantum computers are expected to break — and "harvest now, decrypt later" attacks are already stockpiling encrypted records for that day. Intake.Dental encrypts every patient record with the post-quantum encryption engine from TreeChain, so the PHI you store today stays unreadable decades from now.
Instead of one algorithm guarding everything, TreeChain's polyglottal cipher re-expresses your data across multiple independent cipher alphabets. No single key, algorithm, or breakthrough — classical or quantum — unlocks a complete record.
Every sensitive field — names, birthdates, health histories — is individually sealed into an opaque glyph token on top of AES-256-GCM. A stolen database yields nothing but an unreadable glyph stream, field by field.
每個 Intake.Dental 帳戶都配備雙層 Glyph 加密。額外安全附加服務更進一步 — 鎖定資料庫本身,即使攻擊者取得原始檔案的實體存取權限,資料仍無法讀取。
每項受保護健康資訊皆採用雙層欄位級加密 — 所有方案均免費提供。
每次資料存取、修改和管理操作都會記錄時間戳記、IP 位址和使用者代理。日誌僅供附加且可匯出,供您自行進行合規稽核。
在資料庫、API 和儲存層自動偵測異常。我們的值班團隊會調查每一個警報。
每個帳戶皆採用多因素驗證。基於角色的存取控制,讓牙科助理、櫃檯人員和醫師各自只能查看其角色所需的資料。
每個帳戶都配備我們專有的多語言 Glyph Cipher,疊加於 AES-256-GCM 之上 — 預設雙層加密,專為抵禦未來量子攻擊而設計。
Stored PHI is never wrapped in the RSA/ECC public-key cryptography that Shor's algorithm threatens. The symmetric-first, 256-bit design keeps full strength against quantum search attacks — the same reason NIST rates AES-256 safe in a post-quantum world.
Encryption technology by TreeChain — read the technical deep-dive at treechain.ai
這不是升級 — 而是基本配備。每個診所從第一天起就擁有雙層加密。
在資料庫層本身新增透明資料加密(TDE)。即使駭客取得原始資料庫檔案的存取權限,仍無法讀取任何一個位元組。
可以這樣理解:標準安全對每筆患者記錄單獨加密。額外安全則是同時加密這些記錄所存放的整個保險庫。
