Does Genko Prior Auth fit this practice?
check_fitSay whether Genko Prior Auth supports a practice's specialty (own form, general form, or not supported) and what it offers there, from what the product implements. A payer can be given, but the product does not evaluate payers or payer rules, and the answer says so.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"specialty": "<specialty>"
},
"name": "check_fit"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| payer | No | Optional payer name. The product does not evaluate payers; the answer says so. | |
| specialty | Yes | The practice's specialty in plain words, e.g. 'dental', 'physical therapy', 'aesthetics', 'optometry'. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fit | Yes | dedicated = own code lists and findings form; generic_form = general form; not_supported = no | |
| payer | Yes | ||
| caveats | Yes | ||
| summary | Yes | ||
| page_url | Yes | ||
| next_step | Yes | ||
| specialty | Yes | ||
| what_it_offers | Yes |