Safety & accountability
Clear responsibility before greater delegation.
The RDN remains the nutrition-care professional. Software does not acquire an RDN scope of practice.
Current boundary: shadow mode.
KeyRD currently produces proposals for RDN review. Automated patient contact and changes to practice records remain disabled. The public walkthrough uses fictional records and accepts no patient data.
Professional responsibility stays explicit.
KeyRD is not an independently licensed provider. SUPPORT is constrained to the RDN’s documented nutrition intervention. A new diagnosis, material intervention change, medication decision, concerning symptom, or other professional boundary returns control to the human professional.
Prior silence never increases authority to contact a patient.
Data access is separately authorized.
Shadow mode is not permission to access records. Before identifiable patient information is used, applicable agreements—including a BAA where required—verified access controls, approved configuration, retention and deletion arrangements, and operating safeguards must be in place.
Licensure and liability remain open implementation requirements.
State licensure, attribution of AI-drafted communication, professional liability, supervision, and cross-state workflows must be resolved for the intended use before patient-facing deployment. Statera does not treat those questions as settled by a design principle.
Who is accountable for the product.
KeyRD is a product of Statera Systems Inc., founded by Neil James. James holds a BS in Nutrition & Food Science from LSU and completed the didactic program in dietetics. He is not an RDN. Statera is responsible for the product, its operating boundaries, and the evidence it chooses to claim.
Practicing RDNs are informing workflow and boundary evaluation. Statera will name an RDN or scientific advisor publicly only when that person has accepted a defined role and permission to be identified.
What this page does not claim.
This website does not make a blanket HIPAA-compliance claim or imply an independent security certification.
Report a security concern.
Email a non-sensitive initial description to security@statera.systems. Include the affected page and what you observed. Request an appropriate channel before sharing sensitive details; do not email patient information, credentials, or private records.
If your email app does not open, copy security@statera.systems into your preferred email service. This reporting contact does not authorize access to others’ information or bypassing access controls.