Cortico Beta Features
A Beta feature is a production-available capability that is still under active development and evaluation. It is released to gather real-world feedback, validate clinical and operational usefulness, and identify defects or edge cases prior to general availability.
Key Characteristics
1. Limited Testing
- The feature has undergone internal testing but may not have completed full validation across all workflows, integrations, or environments.
- Performance, accuracy, reliability, and interoperability may vary.
2. Evaluation Intent
- The primary purpose of Beta release is structured evaluation.
- Metrics may be collected to assess usage patterns, effectiveness, and safety.
- Features, interfaces, and behavior may change without notice.
3. Production Use & User Responsibility
- Beta features may be used in live clinical or operational environments at the user’s discretion.
- Outputs must be independently reviewed and verified by qualified personnel before reliance in clinical decision-making, documentation, billing, or patient communication.
- Users retain full responsibility for confirming the accuracy and appropriateness of any outputs prior to use.
4. Liability & Risk Acknowledgment
- Beta features are provided “as-is” and may contain errors or incomplete functionality.
- The organization does not warrant uninterrupted performance, accuracy, or fitness for a specific clinical purpose during the Beta period.
- Use constitutes acknowledgment of increased variability and the obligation to apply professional judgment.
5. Expectations
- Backward compatibility is not guaranteed.
- Workflows may change.
- Support response times may differ from generally available features.
- Data structures and APIs may evolve.
6. Pricing
- Pricing for Beta features may be discounted, included at no charge, or subject to change.
- Final pricing and packaging may differ at general availability.
- Beta Features in particular are subject to significant change in scope and may be significantly pivoted or continued/discontinued based on evaluation.
7. Feedback & Iteration
- Active user feedback is strongly encouraged and may directly shape final functionality.
- Participation in feedback sessions, surveys, or usage reviews may be requested.
- Identified safety or workflow issues should be reported promptly.
A Beta designation indicates progress, not completion. It is suitable for controlled adoption by users comfortable operating with oversight, verification, and iterative change.
