Below is a description of the typical onboarding process for WISHIN Pulse. The process is unique from traditional interface development projects in that:

It leverages your existing interfaces so that you don’t need to develop new interfaces from scratch.

It uses your organization’s sample production data to “reverse engineer” the technical specification for the interface.  In other words, instead of your organization developing an interface based on a technical specification we provide you, we develop the technical specification based on analyzing your data.  We then make modifications on our side to ensure that we are interpreting the data correctly when it comes into the system. This minimizes any interface changes needed by your organization.

If your organization does not have existing interfaces to leverage, WISHIN will provide a specification for the interface and will work with you to ensure the interfaces are developed correctly.

A WISHIN Project Manager is assigned to every participating organization.  The project manager will walk your organization through the entire onboarding process from start to finish.

Step 1:  Data Collection

Interface Assessment

Your organization will complete a pre-analysis questionnaire that gathers information about your current interface structure and details about each interface that will be implemented.

Sample Data Collection

Your organization will collects 10,000 production messages (or 2 weeks of sample messages) per interface that is being implemented.  In addition to the sample messages, 10 printed reports from each interface are also collected.  

Step 2:  Data Analysis (4 Weeks)

Sample Message Review (2 Weeks)

The information and sample messages collected in Step 1 are reviewed and analyzed by WISHIN. Questions arising from the assessment are reviewed and resolved with you.

Code Set Configuration (1 Week)

A code set workbook is developed by WISHIN based on data contained in the sample messages for each interface. The code set workbooks map the discrete data items contained in your organization’s sample message fields to the appropriate values in WISHIN Pulse.  You will review and validates the data mapping contained in the code set workbook.

Draft Interface Specification (1 Week)

WISHIN will create draft interface specifications based on the sample messages and code set workbook.  These interface specifications define the framework for your organization’s interfaces that will populate WISHIN Pulse.  Your organization will review the interface specifications to ensure they are accurate and complete.

Step 3:  Testing (10 Weeks)

Unit Testing (2 Weeks)

The draft interface specifications are tested during unit testing, which is performed by WISHIN’s technical vendor, Medicity.  Any remaining interface issues are resolved between WISHIN and your organization and updates are made to the interface specifications.  Upon completion of unit testing, your organization will review and sign off on the interface specification.

Quality Assurance Testing (4 Weeks)

A quality assurance environment is created by Medicity based on the interface specifications.  Your organization will generate updated sample messages for each interface.  The sample messages will be processed and validated to ensure that they meet the interface specifications and display appropriately in WISHIN Pulse.  Additional sample messages may be required if interface changes are discovered during quality assurance testing.

Participant Testing (4 Weeks)

A certification environment is created by Medicity based on changes discovered during quality assurance testing.  Your organization will direct your production interfaces to the certification environment.  This will allow your organization to view and validate production data while in a test environment.  Additionally, your organization can direct test interfaces to the certification environment which will allow you to leverage any existing test cases you may already have.

Step 4: Go-Live (1 Week)

Upon completion of participant testing the production environment is created.  Your production interfaces are directed to the production WISHIN Pulse server and patient data is available for viewing across WISHIN Pulse.