Before going live with your Corti integrated solution, it is critical to complete User Acceptance Testing (UAT). UAT ensures that the solution works reliably in your environment and integrates seamlessly into your workflows.
This guide outlines the key areas to focus on during UAT to validate your setup and integration with the Corti API.
1️⃣ Verify Firewall Configuration
✅ Ensure your network firewalls are configured to allow connections between your healthcare environment and Corti’s API services.
Review our Firewall Best Practices to confirm all required endpoints are reachable.
If transcripts are not being generated or API requests fail, double-check that your firewall allows outbound connections to Corti's API endpoints.
2️⃣ Validate Transcript Generation and Audio Quality
✅ During test consultations:
Confirm that transcripts are being generated consistently for all recorded sessions.
Review transcripts to ensure accuracy of speech recognition, including medical terminology.
Assess the audio quality—poor audio can significantly impact ASR accuracy.
💡 If transcripts are missing or inaccurate:
Recheck firewall configuration to ensure API connectivity.
Verify that the microphone setup (hardware or virtual, e.g., Citrix redirection) is correctly configured. See:
3️⃣ Confirm Documentation Reflects Consultation Topics
✅ Review the generated documentation for multiple test consultations:
Check that the content covers the topics discussed (e.g., symptoms, assessments, plans).
Ensure that key details from the consultation are captured appropriately by the solution’s templates.
💡 Tip: If you use templates via API, validate that they produce the desired output — see Using Templates to Generate Documentation.
4️⃣ Validate Integration into Your Solution
✅ Ensure that the documentation generated by Corti:
Integrates into your system in the correct fields (e.g., history of present illness, assessment, plan).
Does not overwrite or misplace data within your EHR or clinical documentation system.
👉 Double-check mappings between the API response and your application’s data fields to avoid integration issues.