Issue Triage

Summary

Summary

Information Needed for HealthSparq to Triage:

Key fields to pay attention to within the ticket to facilitate HealthSparq in triaging an issue:

  • Summary
    • High level, concise summary of the issue/issue identified
    • Identify the type of data impacted, such as
      • Provider demographics
      • Negotiated rate error
      • MOOP/benefit API returning incorrect co-pay
  • Description
    • Use this to provide more details about what was searched and the findings.
    • If the issue is impacting all brands (if plan has multiple Brands/LOBs) and should be set at the Parent level, please state it is impacting all brands
    • Please include the internal issue ID your team assigned to the issue for reference.
  • Priority
    • Default is medium
    • Please use the chart on page 21 to determine priority
  • Steps to reproduce
    • This must be completed with detailed steps
      • Include the URL/SSO connection used – provide the full link
      • The test user alias used from your test user list (Pre-Req. Action 3)
      • The test case ID used from the test scenarios you provided (Pre-Req. Action 4)
  • Steps used for test case, example:
    • Dashboard > > Get Cost Estimate > > select Negotiated Rate
      • Search Knee Surgery
    • Review Dr. Freimuth
      • You Pay is $X expected $Y
      • Additional details
    • Actual Results
      • What was returned in search
    • Expected Results
      • What was expected/did not match the actual results (please be specific)
        • Which providers were expected (names, key identifiers)?
        • What negotiated rate (CLNR) or Encounter (NCCT) rate was expected?
        • What MOOP was expected?
      • If referencing the negotiated rate data, please include file name/date (HealthSparq data spec or MRF files) used for validation and how to identify rate/plan/network etc.
      • Our provider data is X, negotiated rate data is Y, our benefit response indicates Z, therefore...
  • Attachments – please include:
    • Screenshots of UI
    • Screenshots of developer tools responses
    • API Response for Member Out of Pocket results
    • Expected Provider Identifiers
    • Test case document (if test case was not shared in Pre-Req. Action 4)
    • SAML if test user is new was not shared in Pre-Req. Action 3)