Optum Device Offset Codes Pair APIs API

The Device Offset Codes Pair APIs API from Optum — 1 operation(s) for device offset codes pair apis.

Operations 1

GET /api/cms/facility/device-offset-code-pairs Fetches the device offset code pairs #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/optum-device-offset-codes-pair-apis-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

optum-device-offset-codes-pair-apis-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: CMS Common Facility Device Offset Codes Pair APIs API
  description: MicroService that contains CMS related information
  contact:
    name: Ken Kracker
    email: ken.kracker@optum.com
  version: v1.0
servers:
- url: /v1/cmscommonms
tags:
- name: Device Offset Codes Pair APIs
paths:
  /api/cms/facility/device-offset-code-pairs:
    get:
      tags:
      - Device Offset Codes Pair APIs
      summary: Fetches the device offset code pairs
      operationId: getDeviceOffsetCodePairs
      parameters:
      - name: sort
        in: query
        description: Any of these (code1,-code1,code2,-code2) are allowed values, default is code1
        required: false
        schema:
          type: array
          items:
            type: string
          default:
          - code1
      - name: limit
        in: query
        required: false
        schema:
          type: integer
          format: int32
          default: 50
        example: 150
      - name: page
        in: query
        required: false
        schema:
          type: integer
          format: int32
          default: 1
      - name: filter
        in: query
        required: false
        schema:
          type: string
      - name: yyyy-MM-dd
        in: header
        description: Date for which historical data is required
        required: false
        schema:
          type: string
          format: yyyy-MM-dd
      responses:
        '200':
          description: Facility - fetch the device offset code pairs
          content:
            application/json:
              example:
                content:
                - code1: C1833
                  description1: Monitor, cardiac, including intracardiac lead and all system components (implantable)
                  code2: 0525T
                  description2: Insertion or replacement of intracardiac ischemia monitoring system, including testing of the lead and monitor, initial system programming, and imaging supervision and interpretation; complete system (electrode and implantable monitor)
                  version: 95
                  offsetamount: '795.62'
                - code1: C1833
                  description1: Monitor, cardiac, including intracardiac lead and all system components (implantable)
                  code2: 0526T
                  description2: Insertion or replacement of intracardiac ischemia monitoring system, including testing of the lead and monitor, initial system programming, and imaging supervision and interpretation; electrode only
                  version: 95
                  offsetamount: '2509.33'
                totalCount: 2
        '400':
          description: 'Bad Request: Filter parameter is invalid'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Notification'
              example:
                error:
                - 'filter : length must be between 2 and 180'
                warning: null
                info: null
        '500':
          description: Interal server error
          content:
            application/json:
              example:
                timestamp: '2024-04-24T06:36:22.518+00:00'
                path: /cmscommonms/api/cms/facility/device-offset-code-pairs
                status: 500
                error: Internal Server Error
                requestId: e36d239e-324
      security:
      - bearerAuth: []
components:
  schemas:
    Notification:
      type: object
      properties:
        error:
          type: array
          items:
            type: string
        warning:
          type: array
          items:
            type: string
        info:
          type: array
          items:
            type: string
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
x-readme:
  explorer-enabled: true
  proxy-enabled: true