SurgeonValue

The rules desk: our checks, for your clinic's agents

Clinics are starting to run software assistants for billing, scheduling and quality work. Those assistants draft well, but they need somewhere to check a rule and get the same answer every time. The rules desk is that place: the same plain-rule checks our pages use, as tools an assistant can call.

Every answer names its source, the date that source was read, what the check cannot tell you, and who has to decide. A check for a person to confirm. The surgeon or the biller decides and signs; nothing here is signed, sent or billed.

What it will not do

No patient details. It takes codes, picks from fixed lists, counts and a hospital name. Any other field is refused, so a note cannot be slipped in, and a refused value is never repeated back.
No model. The answers come from written rules and CMS files, not from AI.
Nothing kept. No account, no sign-in, nothing stored about the caller or the question.
Nothing sent on your behalf. It never files a claim, contacts a payer or signs anything.

The six checks

Check a set of CPT codes for bundling conflicts

ncci_pair_check · The biller's assistant, before a claim goes out.

Before a claim goes: check a set of CPT codes against CMS's NCCI procedure-to-procedure and unit edits for a set list of orthopedic, visit and care codes. Returns conflicts, warnings, and `unchecked` (codes outside that list: not checked, never cleared). Codes and modifiers only.

Needs: codes. Can also take: modifiers.

See the same check as a page

Pick the revision hip or knee code from what was exchanged

revision_joint_code · The coder's assistant, after a revision hip or knee.

For a revision hip or knee replacement: from the joint, side, reason and the parts exchanged, return the CPT code the descriptor supports, the ICD-10-CM code, the side modifier, and the documentation gaps to close. Where the descriptor does not settle the case it says so and picks nothing.

Needs: joint. Can also take: side, reason, exchanged, spacer, graft.

See the same check as a page

Apply the remote therapeutic monitoring billing rules to one month

rtm_month_check · The monitoring coordinator's assistant, when a month closes.

When a monitoring month closes: apply the CY2026 Medicare remote therapeutic monitoring (RTM) rules by who would bill. Returns whether the month can be billed, the rule that decided it, and the codes. An operating surgeon inside the surgical global period cannot bill it. Counts and yes/no answers only.

Needs: biller. Can also take: daysSinceSurgery, globalPeriodDays, deviceDaysThisMonth, managementMinutesThisMonth, isFirstMonthForThisPatient, anotherPractitionerHoldsThisMonth, interactiveContactThisMonth.

See the same check as a page

Find a practice's gaps on the hip and knee outcome measure

proms_readiness · The quality lead's assistant, sizing up the outcome-measure work.

For a practice or its quality lead: from answers about how outcome surveys are collected today, return a gap list against what CMS's TEAM model, Hospital IQR program and ACCESS model require, each line with the CMS document it comes from and one next step. The answers describe the practice, never a patient. Unanswered questions are returned in `unanswered`.

Can also take: joints, teamHospital, survey, preopTiming, riskItems, postop, matched, handoff, nonOp, promis.

See the same check as a page

Look up a hospital in CMS's TEAM participant file

team_hospital_lookup · The contracting or admin assistant, before a hospital conversation.

Is this hospital in CMS's mandatory TEAM episode-payment model? Look one up by its CMS Certification Number (six characters) or by name. Returns the participant row and CMS's preliminary target prices for the orthopedic episode types in that hospital's region.

Can also take: ccn, name.

See the same check as a page

Get the right page to hand a person

human_doors · Any assistant, when the job needs a note read or a signature.

For a job this desk does not do because it reads a clinical note or needs a signature: return the SurgeonValue page to hand the person, and what happens there. Use it instead of sending note text to any tool.

Can also take: job.

Try one

This sends the code-bundling check to the desk exactly as an assistant would, and shows what it gets back.

For your IT person: connect an assistant

The desk speaks the Model Context Protocol (MCP) over plain HTTP. No key, no sign-in. Most assistant tools that take MCP servers accept a setting like this:

{
  "mcpServers": {
    "surgeonvalue-rules-desk": {
      "type": "http",
      "url": "https://surgeonvalue.com/api/mcp"
    }
  }
}

Or call it directly from a script:

curl -s https://surgeonvalue.com/api/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"ncci_pair_check","arguments":{"codes":["27447","99214"]}}}'

It answers initialize, ping, tools/list and tools/call, up to ten requests in one batch. Requests are limited per address. A plain GET to the same address returns a short description. Agents can also read llms.txt and agent.json.

What to know before you rely on it

The bundling check uses the CMS practitioner files effective October 1, 2026, for a set list of orthopedic, visit and care codes. A code outside that list is reported as not checked. CMS replaces the files every quarter.
These are Medicare rules. A commercial payer can apply its own.
Jobs that read a clinical note, such as finding codes in an operative note or drafting a prior authorization letter, stay on our pages, where a person is present. The human_doors check hands an assistant the link to give that person.