C codes now required for specific device-dependent procedures
APCs Weekly Monitor, December 10, 2004
Want to receive articles like this one in your inbox? Subscribe to APCs Weekly Monitor!
C codes now required for specific device-dependent procedures
Q: Are C codes for implants and devices utilized during a device-dependent APC procedure now required for 2005?
A: Medicare has wavered back and forth with C codes for implants and devices since the inception of OPPS in August 2000. But beginning January 1, 2005, Medicare will require 35 selective C codes to be reported with device-dependent APCs. See Table 19 of the OPPS final rule (available in the November 15 Federal Register) for the complete listing of C codes for implants and devices. Medicare resurrected those C codes deleted as of January 1, 2003, with a status indicator of N.
Providers should also note that beginning April 1, 2005, you must report specific HCPCS codes in association with C codes for implants and devices, or they will not pass OCE edits. See Table 20 of the November 15 Federal Register for specific edits.
In the OPPS final rule published November 15, 2004, Medicare stated the following:
The OCE will not go into effect into April 1, 2005. This gives providers the time to prepare for when certain procedure codes must be accompanied by an associated device category code.
Edits will apply at the CPT/HCPCS level rather than APC level.
Edits will not apply when modifiers -73 or -74 are present.
If one device is shown for one APC, that device would have to be billed on the claim for a service in that APC or the claim would be returned to the provider for correction. See Table 20.
If more than one device is shown for one APC, the provider would be required to bill one of the device codes shown on the same claim with the service in that APC for the claim to be accepted. See Table 20.
We are considering expanding the device coding requirements in the future. We believe that requiring device coding for a small subset of device-dependent APCs each year would minimize annual coding burdens and begin to improve data for these APCs, which have consistently proven to be problematic.
Want to receive articles like this one in your inbox? Subscribe to APCs Weekly Monitor!
Related Products
Most Popular
- Articles
-
- HIPAA Q&A: Flu shot requirement for hospital employees
- HealthDataInsights posts new issues for medical necessity claims
- Running an effective peer review committee meeting
- Q&A: Incidental disclosures and patient privacy
- New FAQ posted on storing laryngoscope blades
- Sneak Peek: Effort underway to establish caseload benchmarks
- Tip: Perform your own internal investigation prior to government audit
- What does case-mix index mean to you?
- HIPAA 5010 deadline extended, but threat remains, says AMA
- HHS task force: Consider privacy, security with text messages
- E-mailed
-
- Running an effective peer review committee meeting
- HIPAA Q&A: Flu shot requirement for hospital employees
- What does case-mix index mean to you?
- Featured blog post: Nurses face felony charges after reporting physician to the Texas Medical Board
- HHS task force: Consider privacy, security with text messages
- Tip: Correctly code bilateral pain management procedures
- 2012 CPT code changes for ASCs: Shoulder and knee scopes and pain management
- COT basics to best
- Documentation and coding for toxic metabolic encephalopathy
- Guidance and tact key to compliant, effective physician queries
- Searched