> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.usebridge.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.usebridge.com/_mcp/server. # Triage ## Task types The table below describes each triage task. | Triage Task | Description | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `COVERAGE` | The Patient's insurance is not valid for this Service (see `coverageStatus` within the Service) | | `DATE_OF_SERVICE` | The Date of Service conflicts with the billing date (it may be in the future). If appropriate, [update the Service](/api/api-reference/services/v-2/update-service) with a new `dateOfService` | | `DUPLICATE_SERVICE_TYPE` | The ServiceType cannot be billed again for this Patient (e.g., a second "Initial Visit"). If appropriate, [update the Service](/api/api-reference/services/v-2/update-service) with a new `serviceTypeId` | | `INVALID_INITIAL_SERVICE_TYPE` | This Service cannot be considered an initial service for the Patient. If appropriate, [update the Service](/api/api-reference/services/v-2/update-service) with a new `serviceTypeId` | | `PATIENT_ADDRESS` | An address cannot be resolved, [update the Patient's address](/api/api-reference/patients/update-patient) | | `PATIENT_CONSENT` | One or more [PatientConsent](/api/api-reference/consent/create-patient-consent) is missing or expired for this Patient | | `PATIENT_INSURANCE` | The Patient has an invalid insurance, [associate a new Policy to the Patient's coverage](/api/api-reference/patients/update-patient) | | `PROVIDER_NOT_ENROLLED` | The Provider is not enrolled in the Patient's insurance, so they are not valid for the Service | | `NOTE_SIGNING_PROVIDER_MISMATCH` | The Provider ID listed on the Service is not the same as the Provider ID on the Note signature. [Create a note addendum](https://docs.usebridge.com/api/api-reference/notes/create-note-addendum) to update the note signature. | | `THERAPY_DURATION` | THERAPY_TIME_SPENT_MINUTES is missing from the Note or does not meet the minimum amount required for billing | | `TRIAGE` | This is the fallback task type, consult the message for details. Mark it as `ready` to send to Bridge for review | | `UPDATE_NOTE` | Clinical documentation updates are required. Consult the message in the task for details, then submit a new [NoteAddendum](/api/api-reference/notes/create-note-addendum). | | `BILLING_TIME_LIMIT` | Service cannot be billed more than 75 days after the date of service. | | `MINIMUM_DURATION` | Service cannot be billed if duration of the visit does not meet the minimum requirements. | | `MISSING_ASSESSMENT` | Associated initiating visit is missing required assessment evidence. Update with a [NoteAddendum](/api/api-reference/notes/create-note-addendum) that includes `SCORED_ASSESSMENTS` from the relevant assessment, e.g. SDOH. | | `MISSING_INITIATING_VISIT` | Unable to find an associated initiating visit. If the visit was not within Bridge, submit [NoteAddendum](/api/api-reference/notes/create-note-addendum) with `INITIATING_VISIT_DATE` | | `MISSING_TIME_SPENT_MINUTES` | Service cannot be billed if time spent in minutes is missing from note and note addenda | | `PATIENT_CONSENT_EXPIRED` | One or more of the latest patient consents has expired | | `INVALID_DATE_RANGE` | DATE_RANGE_START and/or DATE_RANGE_END are invalid, consult the message for details | | `INSUFFICIENT_MONITORING_DATA` | 16 unique days of monitoring data are required for billing | | `MISMATCHED_ICD10` | This Service must match the ICD10 codes from a previous Service for diagnosis continuity. Please confirm previous diagnoses, then submit a new [NoteAddendum](/api/api-reference/notes/create-note-addendum) | | `BILLING_FREQUENCY_LIMIT` | This ServiceType cannot be billed again within the given time period (e.g. a second PIN visit within a given month). | | `PATIENT_RECONSENT` | An updated [PatientConsent](/api/api-reference/consent/create-patient-consent) for treatment must be captured due to a change in Providers. | | `PROVIDER_CHANGED` | The Provider for this Service has changed from the a previous Service's Provider. Updated consent must be captured to complete the Provider transition. | | `SERVICE_LOCATION` | The Service Location must include a full billable address (line1, city, state, postal code). [Update the Service](/api/api-reference/services/v-2/update-service) with a complete `location`. | ## Task review Each task on a Service includes: * `ready`: `true` when the task has been sent to Bridge for review. * `inReviewAt`: the time the task was most recently sent for review, or `null` when it is still in the partner queue. Only the generic `TRIAGE` task can be marked ready. Use [Set Ready](/api/api-reference/services/set-ready-service) with `ready: true` to send it to Bridge. Send `ready: false` to return it to your queue. This does not resolve the task or change the Service status. For every other task type, fix the issue described above. Bridge reevaluates the Service and removes the task when the underlying issue is resolved. ## Deprecated Tasks The `REPLACE_NOTE` task is no longer used, and a Note cannot be deleted. All updates should be [NoteAddenda](/api/api-reference/notes/create-note-addendum), identified by the `UPDATE_NOTE` task.