HSC Ticket Updates & Go / No-Go - What to Expect

Summary

Summary

HSC Ticket Updates

  • Current State: Based on your confirmation in the comment section of Execution - Action 2 Ticket on 10/25.
  • We are currently moving forward with one of the following:
    • Options
      • Initiate 500 services block list
      • Provide production data files and approve production release

If “Go" provided in Action 2 Ticket

  • HealthSparq will deploy to production by 11/13
  • Produce updated data for All services in production (if applicable)
  • VERY IMPORTANT
    • If updated data required and will be sent outside of normal monthly schedule
      • Regularly scheduled runs are the 24th, and 25th in the early morning
      • Comment in Execution Action 2 with the production Control File Name/date
    • Updated user interface
    • Messaging to support all services will be deployed (Planning - Action 2)
    • If applicable Your specific block list (Planning - Action 4)
    • If applicable your specific EQ Type and POS overrides (Planning - Action 5)
    • If applicable your specific Service to Specialty Mapping Overrides (Planning - Action 6)

If "No Go" provided:

  • HealthSparq will deploy to production by 11/13:
  • Produce updated data for All services in production (if applicable)
  • VERY IMPORTANT
    • If updated data required requested deadline was Friday 10/27.
      • Regularly scheduled runs are the 24th, and 25th in the early morning
  • Update user interface
  • Messaging to support all services will be deployed (Planning - Action 2)
  • A block list that limits to only the 500 services
  • If applicable your specific EQ Type and POS overrides (Planning - Action 5)
  • If applicable your specific Service to Specialty Mapping Overrides (Planning - Action 6)