51 Authorization Code Verified | Hap
Verify auth details before submission. If appropriate, request a new auth covering the actual services. Scenario C: Medical Necessity Fails LCD The payer may accept the authorization but then apply a Local Coverage Determination that deems the service not reasonable and necessary. Authorization does not override LCDs.
Always consult your MAC’s – it will list every possible HAP code specific to that jurisdiction. Part 8: Frequently Asked Questions (FAQ) Q1: Is a HAP 51 authorization code verified the same as a clean claim? A: No. A clean claim requires no front-end errors and includes a valid auth. HAP 51 says only the auth is valid. Other errors remain possible. Q2: Can a claim be denied after HAP 51? A: Yes. Denials happen at final adjudication for medical necessity, coding mismatches, duplicate billing, or benefit exhaustion. Q3: How long after HAP 51 should I expect payment? A: Medicare fee-for-service claims generally process within 14–30 days. HAP 51 typically appears within 24–72 hours. If no movement after 15 days, investigate. Q4: Does HAP 51 appear on paper claims? A: No. HAP 51 is an electronic transaction code. Paper claims receive no such acknowledgment; you must track via the MAC’s portal or phone line. Q5: What if I receive HAP 51 but later learn the auth was canceled? A: Rare but possible. Auth verification is a real-time check at submission. If a retroactive cancellation occurs, the claim will deny. Use the 276 inquiry close to billing date. Part 9: Future Trends – Will HAP 51 Remain Relevant? As Medicare moves toward prior authorization automation (e.g., the CMS Prior Authorization Initiative for certain services), HAP 51 may evolve into a more substantive step. Some MACs are piloting real-time adjudication where HAP 51 is immediately followed by payment if all other criteria are met. hap 51 authorization code verified
Submit medical records on appeal with documentation supporting necessity. Scenario D: Duplicate Claim If the same claim (same patient, dates, and provider) was already processed, the system may return a duplicate denial despite a verified auth code. Verify auth details before submission
HAP 51 is not a medical necessity determination. Part 7: MAC-Specific Variations Not all Medicare Administrative Contractors handle HAP 51 identically. Below is a summary based on current EDI guides: Authorization does not override LCDs
Resubmit with corrected dates or request an authorization extension. Scenario B: Procedure Code Not Covered Under That Authorization Some authorizations are procedure-specific. HAP 51 only checks the presence of an auth code, not the alignment between the code and the billed CPT/HCPCS. Final adjudication may deny CPT 97110 if the auth was for 97035 only.
The auth had already been used for initial visits. The practice did not realize the auth had a visit limit (12 units). HAP 51 only verified the code existed, not remaining units.
HAP codes range from 00 to 99. Each code conveys a specific status regarding how the payer’s system has processed the initial submission. HAP 51 specifically indicates: "Authorization code verified."
