This month’s product tips and tricks article is around how to integrate our solutions (and why integrations matter!) Integrations are so important, that we’ve even listed it as one of our top 5 advantages of digital transformation. You might have heard your IT department talking about “integrating” your “software systems” and dismissed it as dreaded “tech talk”. Don’t!!! You can use integrations (generally through a Web API) to connect all of your cloud software systems for your healthcare supply chain. This allows you to bridge all of your information into a single place while also triggering actions in different systems.

One of the major advantages to using our entire solution is the ability to streamline all activities in your procurement lifecycle. Even though you may have different teams, stakeholders, and permission sets that restrict users from accessing certain areas of the application, because SpendVu is an integrated solution, you can have requests approved by one stakeholder group and then have projects or contracts automatically created by this trigger.

Integration is the combining of different software components – while each of our solutions are powerful tools that can stand on their own, with integration between these tools you can reduce the time you spend keying in data and ensure that your business processes are following a standardized path. 

I’m going to break down three simple ways you can integrate our solutions to form a powerful healthcare supply chain operations platform.

Method One: Account Integration

spendvu solution integrations

This first method is by far the simplest. If you are a registered user in more than one of our solutions, you can easily save time by logging into VMS only (ProjectVu or ContractVu). You can link your user accounts in order to view the Workflow Dashboard, initiate new requests, and take actions on requests assigned to you, all from the My Workspace tab in VMS.


Method Two: Solution Integration

Another major way to integrate our solutions is to have your projects or contracts created or updated automatically by your RequestVu workflows. In addition to creating a project or contract, you can also have data from the workflow form immediately populate in your new project or contract, saving you time on tedious data entry tasks. Any attachments on that workflow will also be accessible in the project or contract files in VMS so you can access them quickly. To break it down further, a request can:

  • Create a project or contract
    • Trigger a new project or contract to be created and have information from your forms populate into project or contract fields. For example, your request title might become the project name. The product name and product description from a contract request might become the description of a new contract.
  • Send information into an existing project or contract
    • Just like you can populate information from the request form into a new project or contract, you can also send information into an existing project or contract
  • Cancel a project or contract
    • Maybe your request has created a project, but you’ve done some evaluation and determined that you don’t want to move forward with the request. This type of integration allows you to cancel the project or contract at the same time that you are denying the request.
  • Send files into a project or contract
    • When your request is linked with a project or contract any files attached to the request will also be added to the project or contract so you don’t have to navigate between pages to view important materials.

integrate our solutions

Method Three: Data Integration

Integration can also help you maintain lists on your forms. Are you manually managing department codes, approver emails, service lines, etc? Did you know that you can have those lists populate with options pulled from ProjectVu, ContractVu, or even a third party system? A few examples of lists you might use in your form include:

  • Project Names and Numbers
    • If your request is going to add data to an existing project or create a new contract you’ll need to specify a project number. To avoid errors caused by mistyping information, have your form provide a list of all existing projects in ProjectVu to select from.
  • Contract Numbers
    • Maybe the contract your workflow will automatically create is an amendment to an existing contract – this type of list will allow you to easily select the parent contract that your new contract will be associated with.
  • Users Assigned to a Role
    • This type of list gives you so many options. You can pull in a list of users assigned to a specific role from VMS in order to assign steps in your workflow, or you could have users set as assignees when a new project or contract is automatically created by a workflow. This is a great way to ensure the right people are notified when a new project or contract is created.


With so many options for integration you can design the best possible user experience for your requestors, project, and contract managers. And a better experience ultimately means happier teams!