OA-174: Service Not Prescribed Prior to Delivery
Prescription timing issue in a COB scenario. Fix the prescription dating with the primary payer first, then forward to secondary.
What Does OA-174 Mean?
OA-174 appears rarely, typically in coordination of benefits situations where the prescription timing issue affects adjudication across multiple payers. The primary payer flags the timing problem under OA, requiring the provider to resolve the prescription documentation before any payer will process the claim.
CARC 174 fires when the payer determines that the billed service was rendered before a physician prescribed it. This is a prescription timing issue rather than a complete absence of an order (which would be CARC 173). The payer's adjudication system checks whether the prescription date precedes the date of service, and when it does not, the claim is denied under this code.
This denial is most common in settings where services are delivered on an urgent or expedited basis — for example, a DME supplier shipping equipment before receiving the signed order, or a home health agency starting visits before the face-to-face encounter is documented. It also occurs when there are administrative delays in formalizing verbal orders, resulting in the written prescription being dated after services were already rendered.
The code appears predominantly with Group Code CO, making this a provider-side write-off until corrected. Resolution centers on demonstrating that a valid prescription existed before the service date, or on obtaining a retroactive order if the payer's policy allows one. Prevention is straightforward: build workflows that physically block service delivery from proceeding until the prescription is documented and dated.
How to Resolve
Prove the prescription preceded service delivery with dated documentation, or obtain a retroactive order if permitted, then resubmit the corrected claim.
- Resolve with primary payer first Address the prescription timing documentation with the primary payer. Once the primary ERA reflects proper adjudication, forward to the secondary payer.
- Submit to secondary payer Use the corrected primary ERA to submit the claim to the secondary payer with all prescription documentation attached.
Common RARC Pairings
The RARC code tells you exactly what triggered the OA-174:
| RARC | Description |
|---|---|
| N362 | The provider must obtain a signed physician order/prescription prior to dispensing/providing the service or item. |
| N522 | A prescription is required for this service/item. |
How to Prevent OA-174
- Verify prescription dates against service dates before submitting to any payer in the billing sequence
- Maintain consistent documentation standards regardless of which payer is being billed
General Prevention
- Implement a robust system for documenting and tracking prescriptions with timestamps that clearly show the order preceded service delivery
- Establish clear communication channels with referring physicians to ensure all orders are received and documented before services are rendered
- Train staff on proper protocols for verifying prescription status before scheduling and delivering services
- Use electronic order entry systems that require a valid prescription before a service can be scheduled or billed
- Create workflow checkpoints that prevent service delivery from proceeding without a documented physician order
- Stay updated on payer-specific requirements regarding prescription timing and retroactive order policies
Also Filed As
The same CARC 174 may appear with different Group Codes:
Related Denial Codes
Sources
- https://www.mdclarity.com/denial-code/174
- https://x12.org/codes/claim-adjustment-reason-codes
- Codes maintained by X12. Visit x12.org for official definitions.