> ## Documentation Index
> Fetch the complete documentation index at: https://help.clinikehr.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Lab test list

> See every lab request raised in your hospital today, pick one up at the bench, and enter results against its parameters.

export const AuditNote = ({action = 'This action'}) => <div className="ck-callout ck-callout--info" role="note">
    <p className="ck-callout__body">
      {action} is written to your workspace's audit log with your name, the
      record touched and the time — a HIPAA requirement, and one you can review
      yourself under <strong>Audit Log</strong>. See{' '}
      <a href="/platform/security/audit-log">Audit log</a>.
    </p>
  </div>;

export const StillStuck = ({topic}) => <div className="ck-callout ck-callout--note" role="note">
    <p className="ck-callout__body">
      <strong>Still stuck{topic ? ` with ${topic}` : ''}?</strong>{' '}
      Check <a href="/platform/help/troubleshooting">Troubleshooting</a> first —
      it covers the failures we see most often. If that does not resolve it,{' '}
      <a href="/platform/help/contact-support">contact support</a> and include
      your workspace name and the time the problem happened, so we can find the
      matching entry in your audit log.
    </p>
  </div>;

export const TaskHeader = ({before, time, after}) => <div className="ck-task">
    {before ? <div className="ck-task__cell">
        <div className="ck-task__title">Before you start</div>
        <p className="ck-task__body">{before}</p>
      </div> : null}

    {time ? <div className="ck-task__cell">
        <div className="ck-task__title">Takes about</div>
        <p className="ck-task__body">{time}</p>
      </div> : null}

    {after ? <div className="ck-task__cell">
        <div className="ck-task__title">When you're done</div>
        <p className="ck-task__body">{after}</p>
      </div> : null}
  </div>;

export const Path = ({steps = []}) => <span className="ck-path">
    {steps.map((s, i) => <span key={i} className="ck-path__step">
        {i > 0 ? <span className="ck-path__sep" aria-hidden="true">
            ›
          </span> : null}
        {s}
      </span>)}
  </span>;

export const Availability = ({editions = ['all'], plans, roles, note}) => {
  const list = editions.includes('all') ? ['clinic', 'pharmacy', 'lims'] : editions;
  return <div className="ck-avail" role="note" aria-label="Feature availability">
      <span className="ck-avail__label">Available in</span>

      {list.map(e => <span key={e} className={`ck-pill ck-pill--${e}`}>
          {EDITION_LABELS[e] || e}
        </span>)}

      {plans ? <span className="ck-avail__label">Plan</span> : null}
      {plans ? <span className="ck-pill ck-pill--plan">{plans}</span> : null}

      {roles ? <span className="ck-avail__label">Who</span> : null}
      {roles ? <span className="ck-pill ck-pill--role">{roles}</span> : null}

      {note ? <span className="ck-avail__note">{note}</span> : null}
    </div>;
};

<Availability editions={['clinic']} plans="Enterprise" roles="Lab scientists, doctors and nurses" note="Needs the Diagnostics care area" />

The **Lab Test List** is the bench's inbox: **Here's a list of all lab requests for today!** From here you pick up a request, run it, and record what the analyser or the microscope said.

<Path steps={['Sidebar', 'Laboratory', 'Lab Test List']} />

<TaskHeader before="The Diagnostics care area switched on, and at least one lab test in your catalogue" time="A minute to record a result" after="A completed test with a value against every parameter" />

## Before you start

**Laboratory** and **Radiology** come from one switch — the **Diagnostics** care area in **Settings → Facility**. If the group is missing from your sidebar entirely, that is why; see [Care areas](/hospital/get-started/care-areas).

Requests reach this list from a [consultation](/hospital/outpatient/consultation) or a ward chart. To raise one yourself, use **New Test Report**, which opens the ordering form on [Lab reports](/hospital/diagnostics/lab-reports).

## What you're looking at

Above the table sit four controls: **Search for patient**, **New Test Report**, **Refresh**, and **View Columns** → **Toggle columns**, which is how you switch the optional columns on.

| Column                                                   | Shows                                              | On by default |
| -------------------------------------------------------- | -------------------------------------------------- | ------------- |
| **Patient ID**                                           | The hospital number                                | Yes           |
| **Patient Name**                                         | Who the sample belongs to                          | Yes           |
| **Status**                                               | **Pending** or **Completed**                       | Yes           |
| **Conducted By**                                         | The scientist who ran it, or **Not conducted yet** | Yes           |
| **Requested By**                                         | The clinician who ordered it                       | Yes           |
| **Date** · **Patient Type** · **Test Name** · **Result** | Extra detail                                       | No            |

A quiet day, or a hospital that has not ordered anything yet, reads **No recent lab test data available for this clinic.** That is the state a brand-new workspace lands on, and it is correct rather than broken.

<Note>
  This list shows a test as **Pending** or **Completed** only. The richer view — **In Progress** and **Cancelled**, the **Critical** badge, and payment status — lives on [Lab reports](/hospital/diagnostics/lab-reports), which is also where ordering and printing happen.
</Note>

## Run a test and record the result

<Steps>
  <Step title="Open the request">
    From the row's action menu choose **Conduct Lab Test** on a pending request, or **Update Lab Test** on one already completed. **View Lab Results** opens it read-only, which is what a non-lab role gets.
  </Step>

  <Step title="Check you have the right patient">
    The form opens on **Patient Information**, badged **Ward Patient** or **Outpatient**, with the patient ID, name, gender, age and weight. The heading underneath says which — "Ward Patient laboratory testing" or "Outpatient laboratory testing" — because the two go to different places afterwards.
  </Step>

  <Step title="Enter a value for each parameter">
    Under **Laboratory Tests** each test lists its **Test Parameters**. Type into **Enter \{parameter}**, or pick from **Select value** where the parameter is a choice. The reference range sits under the field as **Reference: \{range}**, so you are never converting units in your head.
  </Step>

  <Step title="Submit">
    Select **Submit Lab Results**, or **Update Lab Results** if you are correcting one. You get a confirmation naming the patient type — "Ward lab test results have been submitted successfully".
  </Step>
</Steps>

Reference ranges come from the test definition, not from this form. A test defined without ranges shows none here and prints none on the report, for every patient.

## Sign-out is the step that matters

Entering numbers and *releasing* them are two different acts. A test is only a result other clinicians will act on once it moves to **Completed** — that is the clinical authority step, and it is why **Conduct Lab Test** and **Update Lab Test** are restricted to lab scientists while everyone else gets **View Lab Results**.

<Warning>
  A result that has not been signed out is preliminary. Never hand it to a patient, a ward, an employer or a referring doctor as though it were final — complete it first, or send nothing.
</Warning>

<AuditNote action="Opening a lab request and its results" />

## Who can do this

Your **role** decides whether the **Laboratory** group opens at all, and whether an owner has hidden it from that role under [Role navigation](/hospital/settings/role-navigation). What you may do inside it is decided separately:

| Action                                     | Who by default                         | How it is governed                                                                 |
| ------------------------------------------ | -------------------------------------- | ---------------------------------------------------------------------------------- |
| Open the list and read results             | Clinical and lab staff                 | Role                                                                               |
| **Conduct Lab Test** / **Update Lab Test** | Lab scientists, and the hospital owner | Role — anyone else is told **Only lab scientists can conduct or update lab tests** |
| Order a new test                           | Clinicians and lab staff               | Role                                                                               |
| See the money on a request                 | Staff with billing visibility          | Permission — a figure you may not see renders as a dash, never as a zero           |

Enforcement of the per-person permissions is **opt-in**: someone never saved in the permissions sheet is unrestricted, and the sheet warns **"Saving starts enforcing"**. A **denied action is written to the audit log**; an allowed one is not. Hiding a module from a role's sidebar is a convenience, not a security boundary. See [Staff permissions](/platform/team/permissions).

## Check it worked

* The row's **Status** moves from **Pending** to **Completed**.
* **Conducted By** shows your name in place of **Not conducted yet**.
* Switching on the **Result** column shows the value you entered.
* The result appears on the ordering [consultation](/hospital/outpatient/consultation) or ward chart, under **Results**.

## Common issues

<AccordionGroup>
  <Accordion title="Only lab scientists can conduct or update lab tests">
    Result entry is restricted by role. Ask an owner to set your role correctly, or have a lab scientist enter the values — you can still open the request with **View Lab Results**.
  </Accordion>

  <Accordion title="Please select a lab test first.">
    You reached the results form without a request attached — usually from a stale link. Go back to the list and open the row from its action menu.
  </Accordion>

  <Accordion title="No recent lab test data available for this clinic.">
    Nothing has been ordered, or the search box still has text in it. Clear **Search for patient** and select **Refresh**.
  </Accordion>

  <Accordion title="The parameters I expected are not on the form">
    The form is built from the test's parameter list. Add the missing parameters to the test in your catalogue — see [Lab station](/hospital/diagnostics/lab-station) — and raise the request again.
  </Accordion>

  <Accordion title="There is no Laboratory group in my sidebar">
    Either the **Diagnostics** [care area](/hospital/get-started/care-areas) is off, or the hospital is not on the Enterprise plan. See [Change your plan](/platform/plans/change-plan).
  </Accordion>
</AccordionGroup>

## FAQ

<AccordionGroup>
  <Accordion title="Can I correct a result I already completed?">
    Yes — **Update Lab Test** reopens it for a lab scientist. The change is on the record with your name and the time, which is the point: a corrected result is a new clinical statement, not a quiet edit.
  </Accordion>

  <Accordion title="What is the difference between this and Lab Reports?">
    This list is the day's requests, for the bench. [Lab reports](/hospital/diagnostics/lab-reports) is the full order-to-report surface: ordering, payment, printing, and the richer status and critical-value badges.
  </Accordion>

  <Accordion title="Why do ward and outpatient tests look different?">
    They are filed against different records — a ward request belongs to an admission, an outpatient one to a consultation. The form badges which it is so the result lands in the right chart.
  </Accordion>

  <Accordion title="Does this list include yesterday's requests?">
    It is built for today's work. Use [Lab reports](/hospital/diagnostics/lab-reports) with its period filter, or **Lab Test History**, to look back.
  </Accordion>

  <Accordion title="Who sees that I opened a patient's results?">
    Owners and managers, under [Audit log](/platform/security/audit-log). Every read of clinical data is recorded with your name and the time.
  </Accordion>
</AccordionGroup>

<StillStuck topic="a lab request or result" />