• There are no suggestions because the search field is empty.
SUBMIT

Tips for a Smooth Review Process

Vim
Vim

Ready to submit your app for review? Follow these steps to make the review process clear, efficient, and set your app up for a successful debut.

1. Finalize & Test Thoroughly

Before you submit, confirm that your application is fully tested for security, usability, and performance in the Vim Sandbox environment. Address any issues to ensure a strong first impression.

2. Understand the Submission Process

  • Locking: Once you submit your app for review, changes to this version will be locked during the review period.
  • Iterate if Needed: If you need to make additional updates, simply duplicate the locked (in-review) version to create a new draft and continue improving your app.

3. Prepare All Required Review Details

Providing clear, complete information helps the Vim review team assess your app efficiently and accurately. Here’s what to include and why it’s important:

  • Application Information:
    Briefly describe your app’s purpose, main features, and intended use cases. This helps the review team understand your app’s value and how it fits within the Vim ecosystem.
  • Demo User Credentials:
    If your app requires user authentication, supply demo credentials (username and password) so reviewers can fully test the app’s functionality as a real user.
  • Patient Details (Optional):
    For apps that use patient-specific workflows, provide test patient profiles from your Vim Sandbox EHR. Do not submit real PHI; use only fictitious or test data.
  • Testing Instructions:
    Share clear, step-by-step directions that guide reviewers through the app’s key workflows and features. This ensures comprehensive and accurate testing.
  • Video Demo Link:
    A short video walk-through of your app’s main workflows and value proposition allows Vim reviewers to quickly understand your user experience and features in action. Note: this is for Vim internal teams only; it is important to show the various workflows in your application end to end in the mock EHR. This is not your marketing / demo content. 
  • Permissions & Data Usage:
    List all permissions your app requires (for Vim Hub and EHR resources) and briefly explain why each is necessary. This transparency helps ensure compliance and data security. Note that Vim offers a no-PHI workflow subscription that’s ideal for apps that don’t require PHI, minimizing risk and complexity. Also, you benefit from instant access to HIPAA, SOC 2, and HITRUST certified infrastructure, so you can skip separate security reviews and build with confidence.
  • Technical Point of Contact:
    Provide a dedicated support email so the review team can reach you directly with questions. Timely responses keep your review process on track.

4. Why This Matters

A detailed, well-prepared submission allows Vim to review your app’s security, compliance, and performance more quickly and accurately. This is crucial for a smooth launch and to ensure your app delivers an excellent experience to end users on the Vim platform.