We’ll schedule a UAT session to validate that your app behaves as expected in production EHR environments and is ready for final application review submission.
The goal:
- Confirm your app performs reliably in production EHRs
- Align with the Vim team on how your app is intended to function
- Identify any necessary improvements before moving to formal review
The typical format (45 min):
- Your team will demo the application flow in the Sandbox EHR (approximately 20 min). This helps ensure the Vim team fully understands the intended experience. We’ll also ask clarifying questions as needed.
- We’ll demo your application flow in production EHR environments (approximately 20 min). If your app’s iframe URL is publicly accessible and not blocked by Content Security Policy (CSP), we’ll launch it live within a production EHR (e.g., athenahealth or eClinicalWorks) to validate performance.
- Recap and discuss next steps (approximately 5 min).
The prep:
- Share your demo flow in advance with the Vim team. Please send us the core steps you'd like to walk through (e.g., log into EHR → open your app → perform key actions).
- Ensure CSP whitelisting for production EHR testing
If you’d like to test in production environments, make sure your app’s CSP allows embedding from the following domains, for example below:
json
{
"athena": ["*://*.athenahealth.com/"],
"ecw": ["*://*.ecwcloud.com/", "*://*.eclinicalweb.com/"]
}
Post UAT:
- If no changes are required, or once updates are complete, you’ll be ready to submit your application for formal review that typically takes one week and include compliance, security, and legal validation.