UNSPSC 85694971: Replacement of right finger phalanx with synthetic substitute, percutaneous approach

This classification denotes the group of activities that yields a surgical intervention or procedure to replacement of right finger phalanx with synthetic substitute, percutaneous approach. This surgical intervention or procedure is listed in the World Health Organization's International Statistical Classification of Diseases and Related Health Problems or ICD-10 as code 0PRT3JZ

UNSPSC 85694971 Replacement of right finger phalanx with synthetic substitute, percutaneous approach is a Commodity code nominally describing a surgical procedure, but the recent state and local opportunities tagged under it reflect no medical device or surgical-supply procurement aligned with that specification. Instead, the opportunities span occupational and disability medical evaluation services, pharmacy benefit management, emergency and specialty healthcare for detained youth, and temporary ancillary health professional staffing — none of which involve finger phalanx replacement or orthopedic implants. The code shows a fundamental mismatch between its nominal scope and the actual work being solicited by state and local buyers.

The geographic spread of recent activity includes Arizona (City of Phoenix Retirement Office), California (City of Long Beach, County of Santa Clara Health System), Florida (Collier County), Washington State (Washington State Department of Transportation), and Texas (Harris County Juvenile Probation Department), but the work being procured bears no consistent relationship to the code's stated content. The Washington State Ferries occupational medical surveillance RFP (RFP20260825, due October 9, 2026) and the Phoenix Retirement Office disability medical evaluation RFP (RTMRFP26001, due October 16, 2026) represent the most substantial recent opportunities, each targeting government healthcare administration and employee evaluation services rather than surgical implants or procedure-specific supplies. Because the code's taxonomy label does not map to the actual scope of recent solicitations, pursuit of opportunities under this code on its stated merits is not viable; vendors should verify code assignment in individual RFP documents before investing proposal resources.