Overview

The Service Request tab inside a task is the working area for the request behind the task. Instead of just tracking task status, it lets staff work the underlying request itself — service details, diagnoses, treatments, providers, insurance authorizations, notes, and export to the EHR — all in one place.

A few things to know at a high level: this tab is tied to the service request record associated with the task, so changes here affect the request details, not just the task title or status. Depending on setup, it may also include AI-assisted filling, authorization management, custom fields, and EHR export. If you make changes, click Save Service Request to keep them.

Authorizations section

Near the top, this section manages payer-specific authorization records connected to the service request. Staff can review authorizations by payer; see status (Approved, Denied, Pending, Not Started, Not Required); expand or collapse the view; work with payer-specific details; and create or update authorizations tied to the request.

Each payer can have its own authorization card or expanded panel, and payer tabs can show priority, payer name, and current status. The interface can distinguish between encounter-level and patient-level insurance context. This matters because many service request workflows depend on keeping authorization progress tied to the right payer, and this section lets staff see where the request stands without leaving the task.

Service Request details section

This is the main editable form for the request itself — the core information staff maintain as the request moves through the workflow, and often the source of truth for downstream follow-up, authorization work, and export. Common fields:

• Service Name — the name of the requested service
• Service Type — the category of service
• Request Type — the type of request being made
• Quantity — the requested quantity or units
• Treatments — procedure or treatment codes tied to the request
• ICD-10 Codes — diagnosis codes supporting medical necessity
• Organization — the organization tied to the request
• Requested Timeframe — requested timing window for the service
• Projected Date — the requested service date
• Location or Place of Service — select a location or manually enter the place of service
• Ordering — the ordering provider
• Rendering — the rendering provider
• Notes — free-text notes for request details or follow-up context

Custom fields section

If enabled for that tasklist, the tab can include Service Request Custom Fields for tracking client-specific request information not covered by the standard fields, storing workflow-specific details, and capturing payer or operational information unique to that client's process. Examples: auth subtype, escalation reason, internal checklist values, submission method, or payer-specific notes.

AI fill actions

The tab can include Practice Intelligence fill tools — a general AI fill button for the service request, plus smaller AI fill actions next to specific fields. These can help fill service name, service type, request type, quantity, HCPCS/treatment codes, ICD-10 codes, organization, timeframe, requested date, location or place of service, providers, and notes. This saves time when request details are already present in task context, attachments, or related content. Important: AI fill is meant to assist staff, not replace review — confirm the values before saving.

Export / EHR posting

The Add to EHR button opens the Service Request PDF and posting options. From here, staff may preview the Service Request PDF, choose whether to send the document to the EHR, select the document type used for posting, choose whether to post authorization records to the EHR, select which authorizations to post, and choose whether authorizations post at the patient or encounter level when supported. This is where staff move from working the request internally to sending request data into the EHR workflow, keeping documentation and authorization updates tied together.

Save and unlink actions

At the bottom of the section:

• Save Service Request — saves changes made to the service request fields.
• Export — opens the PDF / EHR export workflow.
• Unlink Service Request — removes the service request association from the task. Use this carefully, as it removes the link between the task and the request.

Best practices

Use clear, specific service names; keep diagnoses and treatments updated as the request evolves; train staff to review authorization status regularly; use notes for important request context rather than just task comments; only use Unlink Service Request when the task should no longer be tied to that request; treat AI fill as a draft assistant, not a final source of truth; and make sure staff understand when to save versus when to export.