Lab Workspace
See how labs set expectations, invite practices, review the inbox, and return clear fixes.
Setup Shapes Intake Quality
The lab side is strongest when setup is treated as operations, not as a one-time admin chore.
Publish Expectations Early
RX forms and supported case types define what the lab wants practices to send before the inbox becomes busy.
Work The Inbox As A Queue
The inbox should help the lab triage and move real work, not bury the team in preventable intake repair.
Where Lab Work Happens
The inbox is the working surface, but it depends on setup that happens before the first case arrives.
For labs, the main place to work is Inbox, but the inbox only works well after the lab has set the foundation around it. Details, location, supported case types, RX forms, and practice invites all shape the quality of what eventually arrives there.
That is why the lab side is more than a queue. It is a controlled way to make expectations visible before practices send the case.
How Labs Set Expectations
The lab should publish clear expectations before asking practices to send cases this way.
The lab setup path matters because it becomes the practice-facing standard later. When the lab uses RX forms and supported case types well, practices do not have to guess what the lab wants or repeat the same clarifying conversation every time.
The best setup is clear enough to improve intake without turning the lab into a form-design project.
How Invites Fit Into The Workflow
Invites connect practices to the lab in a way that improves the submission quality later.
Invites are how the lab brings practices into the same expectations-backed process. That matters because the practice experience gets better when the receiving lab is known early and the packet is prepared with that destination in mind.
Use Invites to connect the right practices to the lab.
Treat invites as part of the operating model, not as a one-time marketing tool.
A connected practice sees the lab relationship earlier and prepares cases against a clearer standard.
How The Inbox Should Be Worked
The lab inbox is strongest when it reflects triage and quality, not repeated intake cleanup.
When a case reaches Inbox, the lab should be able to judge what is ready, what needs review, and what still needs correction before real production work begins. The inbox should feel like a triage queue with clearer packets, not like a holding pen for preventable intake confusion.
This is also why the lab-side setup matters so much. Better setup creates a better queue. Better practice onboarding creates a better queue. The inbox is where the result becomes visible.
How Rejections And Statuses Work
Good review outcomes keep the correction path clear instead of making the team start over from scratch.
If the lab needs a practice to correct something, the goal is to return a clear, structured reason for the fix rather than creating another vague resend loop. The case should remain understandable to both sides, with the lab’s review and the practice’s next action staying tied to the same submission story.
Use structured review outcomes when a case is not ready to move forward.
Keep the case history attached to the same case instead of shifting the conversation into disconnected side channels.
Treat activity as case history and follow-up, not as a substitute for the inbox or the lab setup.