Data responsibility
Healthcare Data Notice
KamiBridge begins with narrow, reviewable workflows and explicit data boundaries. This public website is not an intake channel for patient information.
Effective September 6, 2026
Do not send patient data through this website
Do not enter protected health information, patient names, dates of birth, medical record numbers, insurance identifiers, or identifiable clinical text in the inquiry form or ordinary introductory email. Describe the workflow without patient-level details.
Discovery and demonstrations
Discovery and initial demonstrations use synthetic information. A later evaluation may use appropriately de-identified data or run inside a customer-controlled environment, depending on the agreed scope and applicable requirements.
Written controls before regulated data
- No regulated or identifiable health data should be transferred until roles, permitted uses, hosting, access, retention, deletion, security measures, and incident responsibilities are documented.
- A business associate agreement or comparable data-processing agreement is not implied by this website and must be separately negotiated when applicable.
- Customers remain responsible for determining whether data is properly de-identified and whether a proposed use is legally permitted.
Human review
Workflow outputs are designed to support qualified reviewers with evidence, confidence, and exception handling. They are not represented as autonomous diagnosis, medical advice, final coding, or claim submission.
Minimum necessary scope
Pilots should use the smallest safe data set and the narrowest useful workflow. Production deployment recommendations are based on measured accuracy, failure modes, reviewer impact, and customer-specific governance requirements.
If information was sent by mistake
If you believe patient or other sensitive information was submitted through this website, contact doudou@kamibridge.com promptly with enough information for us to locate the submission. Do not repeat the sensitive content in your message.