Pathology for specialist clinics
Keep every request connected to its results.
Request tests, follow what is outstanding and record review and release decisions in the patient’s clinical context. DappleOS brings pathology follow-through into the same workspace your aesthetic or cosmetic medicine clinic already uses.
At a glance
The request is only the beginning.
What has arrived? What is still missing? Who has reviewed it? Keep those questions connected to the same patient and request.
Request in context.
Select tests and the requesting practitioner from the patient’s record.
Keep missing tests visible.
See partial results and the tests still outstanding against each request.
A place for incoming results.
Find unreviewed results and deliberately link them to the patient and request.
Control what patients see.
Keep result review, portal release and patient notification as separate choices.
See the ordering outcome.
Keep configured electronic ordering and its status attached to the request.
The patient, the practitioner, the request
Start with the context you already have.
For patients whose primary location is in Australia, open pathology from the patient record. Choose the requesting practitioner, select tests and add the details that belong on the request. Internal comments and the follow-up reminder stay separate from information shown to the patient.
Explore the connected clinical record
- Tests that are easy to review
Search available tests, add a configured grouping or enter a custom test name. Selected tests remain visible together.
- Relevant request details
Record clinical notes, billing context and any urgency or confidentiality information. The practitioner decides what is appropriate.
- An internal follow-up point
Set when the request should come back to the team’s attention, without presenting that reminder as a laboratory turnaround promise.
The request carries the right information.
Keep patient-facing request details and internal follow-up comments distinct. Pathology billing context is also separate from submitting a Medicare claim.
Explore Medicare workflowsOutstanding tests
One result arriving does not finish the request.
Keep requested tests and linked results together. A request can remain partly complete while the missing tests stay visible, so the team can see which record still needs a follow-up.
Each requested test keeps its own status.
A new result can arrive while another test remains pending. The record makes that difference visible.
A useful starting point for follow-up.
Review the outstanding work with the responsible practitioner, using the request and its due context.
- Partial completion
The request tracks completion across its requested tests. A linked result and a fully completed request are different states.
- Due dates with context
Due indicators help the team find work to review. An abnormal flag highlights a result for practitioner attention; it is not a diagnosis.
- A deliberate close
A request can complete when all requested tests have linked results, or when an authorised user explicitly closes it.
Incoming results
Received. Reviewed. Connected.
Give incoming results a clear review queue. Filter by requestor, search for a result and confirm the patient, request and relevant tests before saving the link. The record retains who reviewed it and when.
- Find the right work
Use the requestor and abnormal filters alongside search to focus the unreviewed queue.
- Confirm the patient and request
Review the patient context and choose an incomplete or earlier request. Matching remains a deliberate part of the workflow.
- Record the relationship
Select the tests the result belongs to, then save and link. Receipt alone does not establish review or patient release.
Patient access
Review, release and notify are separate decisions.
Decide whether a result is released to the patient portal and whether to trigger the configured patient notification workflow. Keep those choices alongside the reviewed result, with release and reviewer context retained.
- Release is explicit
The practitioner chooses what is shared through the clinic’s patient experience.
- Notification is separate
Selecting notification triggers the configured workflow. Delivery depends on that workflow and its available communication channel.
- Clinical follow-up stays personal
A portal release does not replace the practitioner’s interpretation, conversation or follow-up with the patient.
A clear place for the results you share.
The patient’s clinic-branded view keeps the request and available test results together. It gives them a place to return to the information your practitioner has chosen to release.
Explore your clinic’s patient app
Connected ordering
Keep the hand-off and its status in view.
Use the configured Sonic eOrdering connection where it applies to your clinic. The request keeps an indicator for an order in progress, sent successfully or failed, so the electronic hand-off remains visible.
- Clinic-specific connections
Review your laboratory and requestor setup with the DappleOS team. A custom test entry does not establish laboratory acceptance.
- A clear ordering boundary
A successful electronic order confirms the hand-off. It does not mean the specimen has been collected or the result is ready.
What to review together
Know which request needs the next conversation.
Use outstanding requests, missing-test names and the unreviewed results queue to see the work ahead. Patient, request, result and release information stay connected, reducing the separate lists the team needs to reconcile.
- Outstanding requests
Review missing tests and due-state information with the responsible practitioner.
- Unreviewed results
Check the queue and requestor filter to find results that still need review.
- Recorded decisions
Return to the result’s linked request, reviewer and release context when following up.
Trust and compliance
Clear records. Deliberate clinical choices.
Keep access, patient matching and release choices visible throughout the pathology workflow. Practitioners remain responsible for ordering, interpretation and follow-up.
Feature availability depends on your plan, enabled features and access permissions.
- Encrypted storage
- Authorised access
- Role settings control access to pathology and its clinical records.
- Confirmed context
- The reviewer selects the patient, request and tests before saving the result link.
- Review and release history
- Stored reviewer and release details preserve the context of those decisions.
- Configured connections
- Ordering and notification behaviour follow the clinic’s connected services and workflow settings.
FAQs
How does DappleOS help us follow pathology through?
Requests, requested tests, incoming results and review decisions stay connected to the patient. Your team can see outstanding work and return to the context of a linked result without maintaining a separate follow-up list.
Can our practitioners choose their own tests and request details?
Investigation requests are available for patients whose primary location is in Australia. Practitioners can search available tests, use configured groupings and add custom test names. Clinical notes, billing context, urgency and confidentiality information belong to the request. Laboratory acceptance and the clinical appropriateness of a test remain separate considerations.
Can we see when only some results have arrived?
Yes. Requests retain completion status across the requested tests, with outstanding test names and due indicators. The request can complete when all requested tests have linked results, or be explicitly closed by an authorised user.
How are incoming results matched to the right record?
The review workflow lets the user confirm the patient, choose the request and select the tests a result belongs to. Saving and linking records that relationship and review context. It does not rely on an assumption that every incoming result has been automatically matched correctly.
Are reviewed results automatically shared with patients?
Review, release to the patient portal and notification are separate choices. The practitioner controls release, while notification depends on the configured workflow and channel. Sharing a result does not replace clinical interpretation or follow-up.
Which pathology connections can our clinic use?
DappleOS includes a configured Sonic eOrdering pathway with visible order status. The demo is the right place to review your laboratory, requestor and incoming-result setup. We will walk through the supported connection for your clinic rather than assume every laboratory works the same way.
What can we review in a demo?
Bring your current request-to-result process, including who requests tests, who reviews incoming results and how patients receive information. The DappleOS team can demonstrate outstanding requests, result linking and release choices in that context.
Ask DappleOS
Explore your clinic’s requestors, laboratory connections and review process with Ask DappleOS.
