Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

This screen is the detail and work surface for a single concurrent review at route /cl/utilization-management/reviews/:reviewId.

​
Overview

The Concurrent Review detail page loads a single review from cl_concurrent_reviews by reviewId and subscribes to real-time updates via useConcurrentReviewsRealtime. The page header shows the review_type (formatted by replacing underscores with spaces) and a ReviewStatusBadge. Three summary info cards display: Due date, Payer reference (falling back to useAuthorizationContext), and Approved through date (falling back to authorization context). The page body uses three tabs: Criteria (renders CriteriaResponseForm, edit-gated by cl.reviews.manage), Determination (renders DeterminationRecording, edit-gated by cl.reviews.manage), and Appeals (renders AppealsSection). View-only users see a “View-only access.” message on the Criteria and Determination tabs.

​
Who it’s for

Requires the cl.reviews.view permission to access this route. The Criteria and Determination tabs additionally require cl.reviews.manage to edit content; users without cl.reviews.manage see a read-only message on those tabs.

​
Before you start

  • You must hold the cl.reviews.view permission.
  • The review record must exist in cl_concurrent_reviews; a missing record renders “Review not found.”
  • To record criteria responses or a determination, you must also hold cl.reviews.manage.

​
Steps

1

Open a concurrent review

Navigate from the UM Dashboard worklist or follow a direct link to /cl/utilization-management/reviews/:reviewId. The page loads the review header and summary cards.
2

Check due date and payer context

Inspect the three summary cards: Due date, Payer reference, and Approved through date.
3

Record clinical criteria responses

Select the Criteria tab. With cl.reviews.manage, use CriteriaResponseForm to document responses. Without the permission, a “View-only access.” message is shown.
4

Record a determination

Select the Determination tab. With cl.reviews.manage, use DeterminationRecording to capture the outcome. Without the permission, a “View-only access.” message is shown.
5

Manage appeals

Select the Appeals tab. Use AppealsSection to view or manage appeals associated with this review.

​
Key concepts

The ReviewStatusBadge reflects the status field on the review record. Real-time updates via useConcurrentReviewsRealtime keep the status current without a page refresh.
The page loads authorization context via useAuthorizationContext(review.authorization_id) to fill in payer reference and approved-through date when those fields are not directly set on the review record.
A load error renders a sanitized error message. A missing review renders “Review not found.”

Clinical

Overview of the Clinical core.

Governance & parity

Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/cl.tsx
  • src/cores/cl/pages/ConcurrentReviewDetailPage.tsx
  • src/cores/cl/hooks/useConcurrentReviews.ts
  • src/cores/cl/hooks/useAuthorizationContext.ts