What belongs in a concurrent review record

Concurrent review is the utilization management decision a health plan makes while care is still underway. A hospital stay, a skilled nursing course, a round of outpatient therapy, or a stretch of home health does not get one blessing at the door and then run on trust. The plan looks again, on a schedule, at whether continuing at that level of care still meets the criteria it uses. Each of those looks is its own determination. The record of that determination is what a later appeal, a fair hearing, or an audit can actually read.

The foundation is on the page about what utilization management is. That page names the three moments: before the service, during it, and after it. This page is only the middle one, and only the file. A concurrent review that cannot be reconstructed is a status code. It is not evidence of a decision.

What concurrent review looks like in the working record

The stay is still open. The last review is a line that says continued. The next review date is blank. Level of care is a dropdown copied from admission. When a later denial is questioned, the plan has the admission note and not the reviews in between.

Those are the signs.

A series of decisions, not a copy of the admission note

The admission review answers a different question from the review on a later day of the stay. On admission the question is whether the member met criteria to start at that level of care, given the clinical picture at the time of the request. On a later day the question is whether the member still meets continued-stay or continued-service criteria, given what has happened since. Results have come back. A procedure was done, or it was postponed. Pain, function, oxygen, wound status, or response to treatment has changed. Copying the admission rationale forward, or storing "extend three days" with no new facts, leaves the later decision without a basis anyone else can check.

That gap shows up in a familiar dispute. A plan retrospectively questions days that a concurrent reviewer had approved. Or a facility appeals a continued-stay denial and the file contains a guideline name but not the progress note the reviewer applied it to. In both cases the argument becomes a reconstruction. A reconstruction done months later, from memory or from a chart that has since been amended, is a weaker offer than the record written when the call was made. The point of a concurrent review record is to make the reconstruction unnecessary.

What the concurrent review record contains

A concurrent review record that counsel can offer, and that an examiner can read without interviewing the reviewer, has the same pieces every time. Missing any one of them is how a real clinical judgment turns into a gap.

• The case identity. Enough to match the member, the stay or the course of treatment, the provider, and the date of this review to the authorization that was in force. A free-text nickname in a workqueue does not do that job.
• The level of care and the span. What was requested, what was approved, modified, pended, or denied, and through which date or which number of units. The next review date belongs here, because the approval is for a span, not an open-ended stay.
• The clinical documents actually reviewed. Not a statement that the chart was reviewed. The notes, orders, results, and therapy logs for the days under review, or a precise copy of what was in the file at decision time. Why that copy has to move with the decision is covered in why the clinical record has to travel.
• The criteria, including the edition. The named set, whether that is a Centers for Medicare and Medicaid Services rule, a state Medicaid policy, a plan medical policy, or a licensed criteria set, plus the version in effect on the review date. Criteria change. The edition that mattered is the one the reviewer used that day.
• The application, not only the label. Which elements were met and which were not, in language a second reviewer can check against the documents. "Does not meet criteria" is a conclusion. It is not the application of the criteria.
• Who decided, and on what authority. The reviewer's name and credential. Where the line of business expects a physician, or a clinician in a relevant specialty, for an adverse medical-necessity call, the file shows that person. A queue name with no human credential is not a signature.
• Notices and conversations that count. What was sent to the facility or the member, when, and any peer-to-peer that was offered or held. A phone call that nobody wrote down is not in the record, no matter how clearly the participants remember it.

Level of care, length of stay, and the next review

The usual dispute in concurrent review is not whether any care was appropriate. It is about level and length. Inpatient versus observation. Acute rehabilitation versus skilled nursing. Another day on a medical floor versus a lower level of care that was available. The record has to show the level that was requested, the level that was approved or denied, and the facts that distinguished them under the criteria in force. If the plan approved a lower level, the file should show that the alternative was the determination, not an undocumented preference written nowhere.

The next review date is operational and evidentiary at the same time. Operationally it tells the facility when new clinical information is due. As evidence it marks the end of the span this determination covers. Days after that date are a new decision, with their own documents. Folding them back into an earlier approval, or denying them later without a new review record, is how concurrent files fall apart. A stay of many days is a stack of these spans. The stack, not the admission order alone, is the concurrent record.

When a later denial has to face this file

Retrospective review, after discharge or after the claim, is a real utilization management moment. It is not a license to pretend the concurrent reviews did not happen. If concurrent approvals exist, the retrospective file has to be readable next to them: what was known at each concurrent review, what was approved through which date, and what, if anything, in the completed record contradicts those approvals. A silent reversal, with no new fact and no named reviewer, reads as a missing record rather than as a clinical judgment.

The same is true in the other direction. A continued-stay denial that the facility appeals needs the original concurrent file plus anything new the facility submitted. The appeal layer does not erase the first decision, and the first decision's note is not a substitute for the appeal file. That distinction is the subject of an appeal file versus a note. A concurrent note that says "denied, criteria not met" can point at the work. It cannot stand in for the work when an examiner asks what was known that morning.

What InsuredAudit keeps, and what it does not decide

InsuredAudit is operated by JIL Sovereign Technologies, Inc., a Delaware corporation. It is that company's utilization management record for health plans and for Medicaid and Medicare Advantage managed care. On a concurrent review it binds the determination to the criteria edition and to the documents the reviewer used, at the time of the decision, inside the customer environment. Protected health information stays inside the customer's HIPAA boundary. The point is that the plan can still produce the file, not that the chart was copied somewhere else to prove a point.

The platform does not decide whether the stay met criteria. A qualified reviewer does that. AVA can help explain a denial or draft language for a person to review. AVA does not make the concurrent review determination, and it does not decide the denial. The sealed export, a CREB™ bundle of the utilization management file, is built so counsel can offer it later, with a manifest of what is included. It is not a ruling that a court, an independent review organization, or a hearing officer will admit it, and it is not a ruling that they will agree with the denial. Whether the care met criteria is a separate question from whether the record of the decision still exists.

Questions people ask

What is concurrent review?

Concurrent review is the utilization management decision a health plan makes while care is still happening. A stay or a course of treatment is looked at again, on a schedule, against continued-stay or continued-service criteria. Each look is its own determination, with its own dates and its own clinical picture.

How is concurrent review different from prior authorization?

Prior authorization happens before the service and asks whether to start. Concurrent review happens during the service and asks whether to continue, at what level, and through which date. The admission rationale does not automatically answer the question on a later day.

Does an approved day still need clinical documents in the file?

Yes. An approval is a determination. The file still has to show which documents were reviewed, which criteria edition was applied, who decided, and which span was approved. A status of approved, with nothing under it, cannot be reconstructed later.

Who has to make a continued-stay denial?

A qualified reviewer makes the clinical call, not the software. Many lines of business expect a clinician, and Medicare Advantage expects a physician with appropriate expertise when an adverse determination is based on medical necessity. The record should name the person and the credential the program requires.

Does the concurrent review record decide the appeal?

No. The record shows what was decided at the time, on which facts. An appeal is a later layer. It can add documents and it can reach a different result. It does not erase the concurrent file, and the file does not by itself decide the appeal.