Table of contents

  1. Step 1: Hosting model
  2. Step 2: State IT security approval
  3. Step 3: Internal technical capacity
  4. Step 3a: External assistance
  5. Step 4: Current NBS 6 hosting
  6. Step 5: Case volume
  7. Step 6: Data intake needs (lower-volume jurisdictions)
  8. Step 7: Reporting needs (higher-volume jurisdictions)
  9. Step 8: Data intake needs (higher-volume jurisdictions)

Use this decision tree to identify your recommended starting configuration. Answer each question in order, then validate your recommendation with the CDC NBS team before you begin deployment.

The decision tree identifies a recommended starting point, not a final answer. CDC provides free pre-deployment consultation to help jurisdictions validate their configuration choice. Do not begin deployment without first connecting with the CDC NBS team at nbs@cdc.gov.

Step 1: Hosting model

Is your jurisdiction planning to self-host and self-maintain NBS 7, or will you use a vendor to host or maintain it?

Step 2: State IT security approval

Has your jurisdiction obtained state IT security approval for cloud hosting and the required software technologies (Kubernetes, Terraform, Docker)?

  • Yes, or approval is not required — Go to Step 3.
  • No, or unknown — Begin the approval process now, then continue planning. Approval is required before deployment. Go to Step 3.

Step 3: Internal technical capacity

Does your jurisdiction have IT staff with skills in Kubernetes, Terraform, and cloud infrastructure management, roughly half or more of the required skill set?

Step 3a: External assistance

Will your jurisdiction obtain external assistance from a contractor, vendor, or consultant for deployment and ongoing maintenance?

  • Yes — Go to Step 4. Note that your vendor or contractor must be capable of Kubernetes-based deployments on AWS or Azure. See Vendor-managed deployment for what to look for.
  • No — Stop. Build internal capacity or identify a vendor before proceeding. Contact nbs@cdc.gov for support resources.

Step 4: Current NBS 6 hosting

Where does your NBS 6 currently run?

  • Already on AWS — Lowest migration complexity. Go to Step 5.
  • Already on Azure — Low migration complexity; you will follow the Azure-specific deployment path. Go to Step 5.
  • On-premises — Your migration includes a cloud migration as well as an NBS 7 deployment. Plan for additional time and resources. Go to Step 5.

Step 5: Case volume

What is the approximate annual reportable disease case volume in your jurisdiction?

  • Lower volume (fewer than approximately 50,000 cases per year) — Go to Step 6.
  • Higher volume (50,000+ cases per year), or significant growth expected — Go to Step 7.

The 50,000 case threshold is a planning guideline, not a hard rule. Validate your volume assessment with CDC before making a final configuration decision.

Step 6: Data intake needs (lower-volume jurisdictions)

Does your jurisdiction currently receive high volumes of electronic lab reports (ELRs) or electronic case reports (eCRs)?

  • No — Recommended configuration: NBS Core. Validate with CDC before deploying.
  • Yes — Recommended configuration: NBS Core + DI API. Validate with CDC before deploying.

Step 7: Reporting needs (higher-volume jurisdictions)

Does your jurisdiction need near-real-time reporting — data available within minutes to hours, rather than 24 hours?

  • No — Contact nbs@cdc.gov to discuss your specific needs. NBS Core or NBS Core + DI API may be appropriate starting points.
  • Yes — Go to Step 8.

Step 8: Data intake needs (higher-volume jurisdictions)

Does your jurisdiction currently receive high volumes of ELRs or eCRs?

  • No — Recommended configuration: NBS Core + RTR. Validate with CDC before deploying.
  • Yes — Recommended configuration: NBS Complete. Validate with CDC before deploying.