ሕሙማትኩም ዝያዳ ሚስጢራዊ ሓበሬታኦም ይኣምኑኹም። መድረኽ ከምኡ ንምርኣይ ሃነጽናዮ።
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 ከምኡ'ውን ናይ ገዛእ ርእሱ ንነፍሲ ወከፍ መዝገብ ዳታ ምስጢራዊነት ቁልፊ ብናይ ገዛእ ርእሱ ይምስጠር። ዝኾነ ሓደ ቁልፊ ምስ ዝበታተን፡ ጥራይ እቲ መዝገብ ይቐልዕ — ምሉእ ዳታቤዝኩም ኣይኮነን።
ኣብ AWS እንሰርሕ፡ SOC 2 Type II ምስክር ወረቐትን 99.99% uptime SLA ዘለዎ። ብኣተገባብራ ኢንክሪፕት ዝተገበረሉ ስቶረጅን ኦቶማቲክ failover ዘለዎ ብዙሕ-ክልላዊ ባክአፕ።
Intake.Dental ኣስተዳደርቲ እውን ዘይተኢንክሪፕት ናይ ሕሙማት ዳታ ክረኽቡ ኣይክእሉን። ናይ ዲክሪፕሽን ቁልፍታት ብተናንቲ-ስኮፕ ዝተደረጉን ፈጺሞም ዘይተመዝገቡን እዮም።
ኩሉ ሕቶ — API፡ dashboard፡ form submission — ብ TLS 1.3 ምስ HSTS enforcement ን HTTPS-only delivery ይቐርብ።
ንኩሉ 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 ኢንክሪፕሽን ይመጽእ። እቲ Extra Security add-on ካብዚ ንላዕሊ ይኸይድ — ንዳታቤዝ ባዕሉ ይዕጽዎ ስለዝኾነ ሓደ ጸላኢ ኣብቲ ጥረ ፋይላት ኣካላዊ ምብጻሕ እኳ እንተረኸበ እቲ ዳታ ክንበብ ኣይከኣልን።
ኣብ ኩሉ Protected Health Information ክልተ-ደረጃ ናይ ሜዳ-ደረጃ ኢንክሪፕሽን — ኣብ ኩሉ ፕላን ብዘይ ተወሳኺ ዋጋ ተኣታቲዩ።
ኩሉ ናይ ዳታ ምብጻሕ፡ ምቕያርን ኣስተዳደራዊ ስርሓትን ብታይምስታምፕ፡ IP፡ ን user-agent ይምዝገብ። ምዝገባታት ብmፉሕ-ጥራይ እዮም ናብ ናይ ግዝኣትኩም ናይ ኮምፕላይንስ ኦዲት ምልኣኽ ዝከኣሉ።
ኣብቲ ዳታቤዝ፡ API፡ ን storage layers ኣብ ልዕሊ ኦቶማቲክ anomaly detection። ናይ ኣብ-ጻውዒት ስልጣንና ንኩሉ ምጥንቃቕ ይድህስስ።
ኣብ ኩሉ ኣካውንት ብዙሕ-ደረጃ ምርግጋጽ። ናይ ዓይነት-ዝተመርኮሰ ናይ ምብጻሕ ቁጽጽር ስለዝኾነ ሃይጂኒስቶች፡ ናይ ቅድሚት ዴስክን ኣሓኪምን ንሓደ ሓደ ዓይነቶም ዝሓትዎ ዳታ ጥራይ ይርእዩ።
ኩሉ ኣካውንት ናይ ናትና ናይ ባዕልና polyglottal Glyph Cipher ኣብ ልዕሊ AES-256-GCM ምስ — ክልተ ናይ ኢንክሪፕሽን layers ብነባሪ፡ ኣብ መጻኢ ኣንጻር quantum ጥቃታት ድሕነት ንምሓዝ ዝተሃንደሰ።
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
እዚ upgrade ኣይኮነን — መሰረታዊ ደረጃ እዩ። ኩሉ ክሊኒክ ካብ ቀዳማይ መዓልቲ ክልቲኦም ናይ ኢንክሪፕሽን layers ይረኽብ።
ናብቲ ዳታቤዝ layer ባዕሉ Transparent Data Encryption (TDE) ይውስኽ። ሓደ ሃከር ናብቲ ጥረ ዳታቤዝ ፋይላት ምብጻሕ እንተረኺቡ እውን፡ ሓደ ባይት እኳ ክንበቡ ኣይክእሉን።
ብኸምዚ ሓስቡ፡ Standard Security ንሓደ ሓደ ናይ ሕሙም ሪኮርድ ብግላዊ ይኢንክሪፕት። Extra Security ድማ ንዅሉ ናይቶም ሪኮርዳት መኽዘን እውን ይኢንክሪፕት።
ጋንታና ንናይ IT መራሒኹም ወይ ናይ ኮምፕላይንስ ኦፊሰርኩም ብዛዕባ ቁጽጽርና፡ ናይ ትሕቲ-ፕሮሰሰርስና፡ ን BAA ክገልጽ እዩ።
