VOMS logo  VOMS Organization/Facility Client User Guide (v. July 2018)

VOMS Organization/Facility Client User Guide

The Vaccine Ordering Management System (VOMS) complements the CDC's Vaccine Tracking System (VTrckS). VOMS provides a convenient way to handle orders directly from within the registry.

The goal of the stand-alone VOMS application is to manage inventory for all of the providers in the registry. This allows state and local health jurisdiction administrators to have an electronic visibility to all providers in the state. Other VOMS features include provider agreements and reports.

This is the VOMS Organization/Facility Client User Guide, which covers topics that general users might need to know.

For instructions on administrative/state user tasks such as Approvals & Management and application configuration settings, see the VOMS State User Guide.

VOMS Features

The following are VOMS-related features, although they are not always performed by the same person:

The user access levels and permissions determine what each user can view and do within the application. A user with permission to place orders, for example, may not have permission to approve orders. See the IWeb Administrator User Guide for information about access levels and permissions.

Keycloak Roles and IWeb Access Levels/Permissions

If single sign-on (SSO) is used, the following IWeb roles / access levels / permissions are required for users (Registry Client, Organization Client, and/or Facility Client) to be able to access both IWeb and VOMS through Keycloak SSO:

Note that the optional Keycloak roles to access the various applications should match user permissions when applicable. If IWeb and Keycloak permissions and roles do not match, the user may see a blank screen or not be able to access organizations or facilities.

Access Level Required Keycloak Roles Optional Keycloak Roles to Access Applications

Facility Client

  • Provider Level Permissions
  • Access IWeb
  • Access AFIX (for SMaRT AFIX)
  • Access iQ
  • Access PHC Hub
  • Access VOMS
  • Provider Interface Profile Form

Organization Client

  • Organization  Provider Content (data) Security
  • Access IWeb
  • Access AFIX (for SMaRT AFIX)
  • Access iQ
  • Access PHC Hub
  • Access VOMS
  • Provider Interface Profile Form

Registry Client

  • State Level Permissions
  • Access IWeb
  • Access AFIX (for SMaRT AFIX)
  • Access iQ
  • Access PHC Hub
  • Access VOMS
  • Provider Interface Profile Form

There are two methods by which these roles can be assigned:

Note that users with View permissions (Registry View, County View, Organization View, and Facility View) are not able to access the VOMS application.

Supported Platforms

The supported platforms for VOMS are as follows:

What Supported Notes

Number of instances

Single

 

Java server platform

Node 6.9.1

 

Operating systems

  • Linux

 

Minimum RAM

8 Gb+

 

Minimum disc size

1 TB

 

Minimum processor

2 Quad Core 64-bit processors

May be deployed on existing servers.

Application server

N/A

 

Database

Oracle 12c

 

Web browser

Internet Explorer 11

As of January 2016, Internet Explorer 8, 9, and 10 are no longer supported.

STC | One logo