Issues are currently in beta and subject to change. During the beta period, issue creation is limited to EDI error reports.

An Issue is a record of a problem with a member’s coverage, eligibility, or demographic data. It is often raised by a carrier or partner and may require action in order to resolve.

Origination

Issues can originate from a variety of places:

  • EDI error reports
  • Carrier API responses (e.g. EOI requirements)
  • Manually by Noyo Operations (account-dependent)
  • Snapshot processing errors (e.g. mapping errors)

During the beta period, Issues are only created from uploaded carrier EDI error reports.

Shape

Here’s an example of an Issue object in the Noyo API:

{
  "carrier_id": "6f1b3f70-95db-4aef-9fde-7c3e10cac11b",
  "carrier_issue_code": "0270",
  "carrier_issue_details": "Dependent not eligible per employee coverage level (tier). This error will occur when you report dependents who are not covered, according to the employee's members covered code (tier).",
  "created": 1747085625,
  "employee_id": "1d09d9a6-60fc-4147-ba3f-65004aff647d",
  "group_id": "7464dfc7-375b-4f8c-bc6f-ef5f89277fab",
  "id": "57ece5b7-1a40-4015-96d6-a5d952c7a3e8",
  "issue_key": "b161ed48ab8edcaa47f22c78af79c04d4649c0fecb5467905d45c98be24fc447",
  "last_seen": "2025-05-13T17:27:11.523459+00:00",
  "member_id": "1d09d9a6-60fc-4147-ba3f-65004aff647d",
  "member_type": "employee",
  "originating_record_type": "partner_document",
  "resolution_method": "partner_document",
  "resolved_at": "2025-05-13T17:27:11.523459+00:00",
  "status": "resolved",
}

Lifecycle

Member Matching

Issues are also automatically matched to employees and dependents in Noyo. When the issue source is a carrier-provided document that doesn’t use Noyo IDs or the custom_individual_id field, members are matched using their name, date of birth, and other identifying information like carrier-assigned ID or SSN.

Issue Matching and Resolution

Issues are automatically matched to previous issues to update or resolve them. If the same issue is found in a new upload or transmission, it will not be duplicated. If the issue is no longer found, it will be automatically resolved.

Dismissing Issues

If an issue doesn’t need to be addressed, it can be dismissed. Dismissed issues are not visible by default in the app, but can still be returned by the API when not filtered.

Roadmap

We are actively working on expanding the feature set for Issues, including:

  • More issue sources (e.g. carrier API responses)
  • Severity and type classification
  • Issue assignment (in-app only)
  • Automatic ingestion from carrier systems
  • Integration with Dynamic Configuration
  • Integration with Tracking

API Reference