
Prices, ASC markets & policy
Explore healthcare prices and public data with ten read-only tools from Techy Surgeon. Price Atlas helps you discover supported procedures, choose an exact code and hospital care setting, and compare posted commercial facility rates in a US city, state, supported market or hospital.
Example path ·
https://techysurgeon-mcp.netlify.app/policy/mcpPolicy Radar also provides source-linked Open Payments aggregates and an integrated surgery-market comparison. Use for one or two market briefs instead of opening separate ASC and workforce cards. Use for its supported general-payment cohorts and filters, preserving category and coverage limits. For a requested Open Payments aggregate view, return one initial result card. Annual trends are already available through the card's group controls; do not prefetch another trend result merely to make trends available or broaden a company view into a specialty trend. Issue another result-producing call only when the user explicitly requests results of an additional distinct comparison. Use as a data-only helper when procedure discovery is needed; it is not clinical code advice. Aim for one outcome-oriented app card per objective; supporting lookups should not create additional screens. Price search summaries cover all matching rates in the catalog before pagination; catalog coverage is not complete market coverage. Policy Radar covers Medicare alternative payment models (TEAM, CJR-X, ACCESS, BALANCE), ambulatory surgery center markets, orthopaedic workforce by county, open CMS/FDA rulemaking, and hospital procedure prices through Price Atlas. Answer the user's actual question with the minimum relevant lookups; do not open unrelated tools to demonstrate capabilities. Hospital identity and model explanations return evidence without a card. Reuse a resolved CCN rather than repeating identity searches. Use only for posted hospital facility prices for a procedure and US place; compare only the returned code and care setting. An episode benchmark, target, spending, loss or downside-risk question is not a commercial-price question. This connection has no hospital-specific episode targets, episode spending or financial-risk ranking. Explain that limit and use the returned CJR-X website link when relevant; do not substitute Price Atlas rates or keep searching prices for those missing metrics. When a resolved hospital has no price coverage, report that limit instead of retrying its name or CCN. Hip and knee searches may resolve to the same MS-DRG: do not retrieve identical code, setting and location evidence twice. For a price histogram, use returned full-query histogram bins, never the preview rows or reconstructed min/median/max. If the user says my area with no explicit location in the conversation, ask only for city and state; this feed does not accept ZIP or radius. Cash/self-pay and insurer-specific rates are unavailable, so never offer a cash-versus-insurance choice or promise those outputs. Never present a reported facility rate as a personal cost estimate. Always show source links and data limits. It does not give legal, billing or clinical advice and holds no patient data. To check model participation for a named hospital whose CCN is unknown, call first, then .
2 in the ChatGPT listing