MyVoice.Signlanguageandmultilingualmessagingasafirst-classinterface.

MyVoice also carries the written conversation. A patient writes in their language. A clinician reads in theirs. The message routes to the right care team member based on clinical content, and consent is granular per thread and per participant. A family member can be added with the patient's consent for a single conversation, a single episode, or for the length of a care plan, and that consent is reversible at any time. The thread is captured in the longitudinal record and surfaces back during the next visit.

Most clinical software treats deaf, hard-of-hearing, and limited-English patients as a secondary case. MyVoice treats sign language and a patient's own spoken language as first-class interfaces. Deaf veterans, deaf members of the public, deaf clinicians, and patients who speak any language get a direct conversation with the platform without waiting for an interpreter. Accessibility is the floor, not a feature ticket.

MyVoice runs inside Dr. Kai and inside the ministry-facing dashboards a deaf clinician uses. Wherever the Hydor platform has a conversation, MyVoice can carry it in sign language or in the patient's own written language. It is a module, not a separate product. MyVoice runs on the Conversational Intelligence layer, the same engine that powers Dr. Kai on a wearable. Sign, spoken, and written language share one substrate.