Pathology for specialist clinics
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
What has arrived? What is still missing? Who has reviewed it? Keep those questions connected to the same patient and request.
Select tests and the requesting practitioner from the patient’s record.
See partial results and the tests still outstanding against each request.
Find unreviewed results and deliberately link them to the patient and request.
Keep result review, portal release and patient notification as separate choices.
Keep configured electronic ordering and its status attached to the request.
The patient, the practitioner, the request
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
Search available tests, add a configured grouping or enter a custom test name. Selected tests remain visible together.
Record clinical notes, billing context and any urgency or confidentiality information. The practitioner decides what is appropriate.
Set when the request should come back to the team’s attention, without presenting that reminder as a laboratory turnaround promise.
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
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.
A new result can arrive while another test remains pending. The record makes that difference visible.
Review the outstanding work with the responsible practitioner, using the request and its due context.
The request tracks completion across its requested tests. A linked result and a fully completed request are different states.
Due indicators help the team find work to review. An abnormal flag highlights a result for practitioner attention; it is not a diagnosis.
A request can complete when all requested tests have linked results, or when an authorised user explicitly closes it.
Incoming results
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.
Use the requestor and abnormal filters alongside search to focus the unreviewed queue.
Review the patient context and choose an incomplete or earlier request. Matching remains a deliberate part of the workflow.
Select the tests the result belongs to, then save and link. Receipt alone does not establish review or patient release.
Patient access
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.
The practitioner chooses what is shared through the clinic’s patient experience.
Selecting notification triggers the configured workflow. Delivery depends on that workflow and its available communication channel.
A portal release does not replace the practitioner’s interpretation, conversation or follow-up with the patient.
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
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.
Review your laboratory and requestor setup with the DappleOS team. A custom test entry does not establish laboratory acceptance.
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
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.
Review missing tests and due-state information with the responsible practitioner.
Check the queue and requestor filter to find results that still need review.
Return to the result’s linked request, reviewer and release context when following up.
Trust and compliance
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.
Medical Board of Australia
Keep requests, incoming results and review context together to support the clear, timely records described in Good medical practice. The practitioner remains responsible for assessment and follow-up.
Read the code of conductServices Australia
Keep patient, requestor and test details in the request workflow. Your clinic should review the requirements for pathology requests, including the patient’s choice of collection centre and the electronic request arrangements it uses.
Read request guidanceYour clinic applies the guidance relevant to each practitioner and treatment. Clinical decisions and compliance remain with your team. DappleOS is not endorsed by these regulators.
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.
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.
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.
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.
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.
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.
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.
Explore your clinic’s requestors, laboratory connections and review process with Ask DappleOS.
