---
title: "Which X12 claim status and acknowledgment transactions are supported by Claim.MD?"
slug: "which-x12-claim-status-and-acknowledgment-transactions-are-supported-by-claimmd"
updated: 2026-01-05T18:36:07Z
published: 2026-01-05T18:36:07Z
canonical: "docs.claim.md/which-x12-claim-status-and-acknowledgment-transactions-are-supported-by-claimmd"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.claim.md/llms.txt
> Use this file to discover all available pages before exploring further.

# Which X12 claim status and acknowledgment transactions are supported by Claim.MD?

**Question:** Does Claim.MD support X12 transactions such as 276, 277, 278, or 999 through the API?

**Answer:** Claim.MD handles claim status and acknowledgments differently than traditional X12 workflows:

- **276 (Claim Status Request):** A 276 request is not required when using Claim.MD. Claim status updates are automatically returned without the need to submit a status inquiry.
- **277 (Claim Status Response):** 277 transactions are available through **SFTP only**. When using the API, claim status information is returned in **JSON or XML** format instead of X12.
- **278 (Referral Authorization):** 278 transactions are not supported by Claim.MD.
- **999 (Implementation Acknowledgment):** 999 transactions are not returned. Rather than rejecting an entire file due to a small claim-level issue, Claim.MD returns rejections at the **individual claim level**. In the event of a significant file-level issue, an error is returned in a `.result` file instead.

This approach allows for more granular error handling and avoids unnecessary rejections of entire files due to isolated issues.