Phase 3: New Site Steps to Validate

A CDC job aid to support site administrators

Purpose

Validate is the third of four onboarding phases for the NSSP BioSense Platform. This stage is important, because files cannot be processed unless the format and naming convention are valid.

Magnifying glass with checkmark on blue background

The process

This content is part of a series of online job aids related to onboarding. These resources are meant to be used together along with New Site Onboarding — The Complete Guide.

Download this job aid: Phase 3: New Site Steps to Validate

This guide will take site administrators and feed administrators through activities that must be completed before connecting to the BioSense Platform production environment. Before proceeding with the Validate phase, make sure your facility successfully submitted a "Hello World" test message to confirm feed connectivity (see Phase 2: New Site Steps to Connect). Sometimes the site administrator will oversee the feed administrator's tasks.

Graphic showing onboarding phases
During this phase, it is important to ensure data contain the minimum required personally identifiable information (PII).

Both site and facility follow these steps:

STEP 1: Verify that file format and naming conventions are valid (see Onboarding Guide, Section 4.4, "File Format and Naming Conventions"). Each feed must submit a valid test message to the BioSense Platform. Files uploaded to the BioSense Platform cannot be processed unless file format and naming convention are valid.

  • Log in to your feed's account in Staging using WinSCP or FileZilla.
  • Upload a valid message with the correct file name convention and correct batch and message structure.

STEP 2: For each feed, set up a schedule for batch transmissions using these options:

  • Transmit in 15- to 60-minute increments (preferred)
  • Transmit at least once every 24 hours

STEP 3: Review data. Make sure data being sent contain the minimum required personally identifiable information (PII) and that data elements are mapped correctly.

STEP 4: Submit data for validation.

SITE ADMINISTRATOR FEED ADMINISTRATOR
STEP 5: Do facility data meet NSSP-required minimums for validity and complete?
  • Priority 1 data elements for NSSP onboarding to production should meet 80% threshold.
  • Priority 2 data elements should meet threshold within 12 months of completing onboarding to production.

Until the SAS Staging Data-Quality-on-Demand tool is released, please contact the NSSP onboarding team to obtain data quality reports.

STEP 5: Request data validation through the site onboarding coordinator.
STEP 6: Do facility data meet site-specified minimums? STEP 6: Correct reported HL7 issues, if applicable. Resubmit corrected data for validation.
STEP 7: As needed, work with facility to fix HL7 issues and resubmit corrected data. STEP 7: Once NSSP approves the facility for production, work with the site administrator to configure the feed to point to the production environment and proceed with live data flow.
STEP 8: Site Sign-Off: For help with data validation and production sign-off, contact the NSSP Service Desk.
  • Final sign-off from onboarding team is required before proceeding with facility activation.
  • The onboarding team will validate data and provide results to the site administrator.
STEP 9: Facility Activation: Once data meet NSSP and site-required minimums for onboarding:
  • Update Facility Status to Active in the Master Facility Table (MFT). This prepares the facility to receive data in the production environment.
  • Check request status. The onboarding team will run a final validation on data and either (1) approve activation request or (2) decline activation request and return rejected info to site for review.
STEP 10: Once the facility is approved for activation in MFT, work with the feed administrator and onboarding team to configure feed to point to production environment. Proceed with live data flow.
  • HL7® and FHIR® are the registered trademarks of Health Level Seven International, and their use of these trademarks does not constitute an endorsement by HL7.