Clinical Rounds

Terms of Service

Professional conditions for using the Clinical Rounds teaching workspace.

These terms are written for the product you are building: a clinical learning platform with generation, analytics, review, community pages, and future authenticated data services. They define acceptable use, operational boundaries, and the relationship between prototype behavior and final production implementation.

1. Educational use

Clinical Rounds is designed for training, simulation, reasoning review, and faculty-led assessment workflows. It is not intended to replace real-world clinical judgment, institutional protocols, supervision, or patient-care systems. Cases and outputs are educational artifacts.

2. Account responsibility

Users are responsible for controlling access to their accounts, protecting authentication methods, and using appropriate institutional credentials. Faculty, residents, and administrators should access only the areas of the workspace that correspond to their role.

3. Generated content

Generator outputs, scenario previews, review notes, and analytics surfaces are provided to support learning and iteration. The platform may produce incomplete or draft-level content in early prototypes. Before any production deployment, institutions should validate generator behavior, review defaults, and audit rules against their own teaching standards.

4. Restricted behavior

  • Do not use the platform to claim patient-facing diagnostic authority.
  • Do not attempt unauthorized access to institution workspaces, analytics, or debug views.
  • Do not misuse faculty review tools, audit records, or learner analytics for purposes outside sanctioned educational workflows.
  • Do not redistribute protected institutional content without authorization.

5. Prototype and production distinction

The current HTML prototypes establish design, page structure, and product flow. They do not by themselves provide full authentication, session governance, or production persistence. Those responsibilities will be completed during migration into the Next application and connected services. By using the prototype, stakeholders acknowledge that some actions are simulated until the integrated version is deployed.