Right Kidney: Length 11 cm (normal).Volume 115.1 cc.Endometrium: 8 mm (normal).Status: ABNORMAL.
Ultrasound reporting, modernised
Ultrasound reports that write themselves.
QualiScan turns structured worksheets into clean narrative reports, in your radiologists’ own style, verified by your radiologist before they leave. Works alongside any RIS and PACS, with nothing installed.
Open the demo. It runs on synthetic data only.
Example of QualiScan at work, on demonstration data: a renal worksheet with length 11 cm, width 5 cm and AP 4 cm, and the size category the sonographer selects, normal. The narrative report is then generated from the deterministic template, findings first and a conclusion of no abnormality seen, ready for the radiologist to verify.
The problems we solve
Reporting software shouldn’t be the hardest part of the scan.
Priced for hospital networks
Enterprise contracts and big upfront costs keep modern tools away from smaller practices.
With QualiScan: A subscription that scales with your monthly report volume.
Months to roll out
Conventional systems are an IT project before anyone reports a single study.
With QualiScan: Sign in from a browser and report. Nothing installed, and no changes to machines, PACS or RIS.
Rip and replace
Most platforms want to take over your stack instead of fitting into it.
With QualiScan: QualiScan works alongside any RIS and PACS you already run.
Reports that read like fragments
Rigid templates output data, not the prose radiologists actually write.
With QualiScan: Narrative findings and a proper conclusion, in your radiologists’ own style.
Workflow
One clean flow: capture, check, report, verify, release.
01Capture
A sonographer picks up a case from the shared worklist and fills in a structured worksheet.
02Check
Where your practice sets rules, they show what is missing or contradictory on the worksheet: a required field blocks the send until it is recorded, and a finding on the other side from the study’s side is a hard stop.
03Report
The report is generated from a deterministic template in your radiologist’s own reporting style: narrative findings and a proper conclusion. The same input always produces the same words.
04Verify
Your radiologist reviews, amends if needed with the original preserved and the changes shown, and verifies. Verified reports carry a VERIFIED REPORT block; anything unverified is marked PRELIMINARY REPORT.
05Release
The verified report leaves as a PDF, a print, or a one-click copy of the report text, placed into your RIS the same way a typed report would be.
- 01Capture
A sonographer picks up a case from the shared worklist and fills in a structured worksheet.
- 02Check
Where your practice sets rules, they show what is missing or contradictory on the worksheet: a required field blocks the send until it is recorded, and a finding on the other side from the study’s side is a hard stop.
- 03Report
The report is generated from a deterministic template in your radiologist’s own reporting style: narrative findings and a proper conclusion. The same input always produces the same words.
- 04Verify
Your radiologist reviews, amends if needed with the original preserved and the changes shown, and verifies. Verified reports carry a VERIFIED REPORT block; anything unverified is marked PRELIMINARY REPORT.
- 05Release
The verified report leaves as a PDF, a print, or a one-click copy of the report text, placed into your RIS the same way a typed report would be.
The report difference
From fragments to findings.
- Narrative prose in your radiologist’s own reporting style, tuned from their sample reports
- A proper CONCLUSION section, not a status dump
- Deterministic output: the same input always produces the same words
- Recorded-only reporting, if your practice chooses it: a field left blank says nothing, and never turns into a normal finding by itself
- Amend before sign-off, with the original preserved and the changes shown
FINDINGSThe right kidney is enlarged, measuring 13cm. The left kidney is normal in size. Normal corticomedullary differentiation.There is moderate right hydronephrosis.There is no calculus.There is no parenchymal mass seen.The bladder is normal and emptied completely.No other urinary tract pathology.CONCLUSIONEnlarged right kidney.Right hydronephrosis.No other urinary tract pathology.
Demonstration data
With recorded-only reporting, a field left blank says nothing in the report, and the closing line appears only once every visible field is recorded.
Checks
Checks before a report leaves.
Your practice writes its own rules, per exam type and per field, at onboarding, and chooses the exam types the consistency checks run on. The checks say only what is missing or contradictory on the worksheet: they never say a finding is clinically wrong, and never write or propose a conclusion.
- A required field blocks sending to the radiologist until it is recorded. A reminder is shown and never blocks; an optional field does neither.
- Where your practice switches the consistency checks on for an exam type, a finding recorded on the other side from the study’s side is a hard stop: the study cannot be sent or signed until the worksheet is corrected.
- With the consistency checks on, a conclusion that names only the opposite side, a normal-study conclusion beside an abnormal finding, or a required measurement left empty is a warning your radiologist acknowledges with a reason, recorded in the audit trail.
- Administrators see completeness across the worklist.
- Where your practice sets billing rules, captured billing items are checked against them as flags only: nothing blocks a sign-off, and QualiScan makes no claim.
- A reminder, switched on per exam type, can name the fields still unrecorded before the study leaves the worksheet. Medicare number and IRN formats are checked as they are entered, for Australian practices.
Example on demonstration data: a renal worksheet’s checks show the left kidney length as required and not yet recorded, so sending to the radiologist is blocked, and clinical history as a reminder. At sign-off, the radiologist has acknowledged a warning about a normal-study conclusion beside an abnormal finding, with a typed reason, recorded in the audit trail.
Annotations
Mark where the finding is.
Where your practice switches annotations on, a sonographer can mark where a finding sits on a fixed schematic diagram of the thyroid, liver, kidneys, breasts or scrotum. The mark is recorded with the study. The report gains one sentence on that finding’s own line and one small figure under the findings, on screen and in the PDF, and the structured export carries each mark with its region and its label. The conclusion never speaks a mark.
Marks on the diagramThyroid
- Nodule 1: right lobe, upper third
- Nodule 2: left lobe, lower third
Added to the finding’s lineMarked on the diagram: right lobe, upper third.
Demonstration data
Recorded, not computed. A mark records a place on the diagram. Nothing is computed from it: never a measurement, a size, a category, a grade or a probability.
Roles
Built for the whole team.
Sonographer
Claim studies, fill structured worksheets, attach reference images where your practice turns the image store on, and submit for review.
Radiologist / Reviewer
Review submitted studies, amend the generated text with the changes shown, acknowledge any check warning with a reason, and verify reports, with any reference images alongside.
Administrator
Everything above, plus user management, the cross-study audit view and the practice data export, with QualiScan Insights, the report archive and the report API and its keys where your practice switches them on.
Every submit, sign-off, amendment, acknowledgement, export and API key event is recorded in the audit trail: who, what and when, across all studies. The original generated text is preserved beside any amendment.
QualiScan Insights
Your practice’s workflow, in counts and times.
An administrator’s dashboard over your practice’s own recorded workflow activity, read from the records your practice already keeps, including the same audit trail that records every submit and sign-off. Every figure is a count or a time: never a clinical judgement, and never a patient’s name or identifier. Switched on per practice.
- Completeness at send: the share of a worksheet’s visible fields recorded when the study is sent, and the share of studies sent with nothing unrecorded.
- Turnaround: the sonographer stage, the radiologist stage and the total, each as a median and a 90th percentile.
- Edits per report: reports amended before sign-off, with the findings or the conclusion rewritten, and the checks acknowledged per sign-off.
- Volume: studies created, sent and signed, per day, per exam type and per staff member.
- Billing: records ready for export and records exported.
The last 7, 30 or 90 days or a custom range, filtered by exam type or staff member. Every figure’s definition is on the page, and each exports as CSV, every export recorded in the audit trail.
Example dashboard on demonstration data, last 30 days: 96.8 per cent of visible fields recorded at send on average, 22 of 25 studies sent with nothing unrecorded; 3 of 21 reports amended before sign-off; turnaround medians of 2.1 hours for the sonographer stage, 18.4 hours for the radiologist stage and 20.7 hours in total; 27 studies created, 25 sent and 21 signed; 4 billing records ready for export and 17 exported.
Exam types
31 exam types across eight families, ready to report.
- Musculoskeletal
- Abdominal and organ
- Renal
- Thyroid
- Vascular
- Obstetric
- Gynaecological
- Procedure notes
A structured worksheet and a deterministic report template for each exam type, tuned from your own radiologist’s sample reports.
Integration
Works alongside your systems.
QualiScan puts the ultrasound worksheet, the completeness checks and the report in one place, in your radiologist’s own words, ready for the PACS and RIS you already run. One deployment per practice, every site in your group, every ultrasound exam type you report, and only a small connector to install at the site.
Delivery of the finished report into a practice’s PACS and RIS is scoped per practice and not live anywhere today; reports leave today as PDF, print, copied text and the billing export.
Three ways to run QualiScan
- 01Today
Standalone
Sonographers fill worksheets and your radiologist verifies reports in a browser. Nothing is installed, and nothing changes on your machines, your PACS or your RIS. A verified report leaves as a PDF, a print or a one-click Copy report text, letterhead and referrer included, placed into your RIS the same way a typed report would be, with typing support for that step.
- 02In build
QualiScan Connect
A small connector at your site, one per site. Through it your ultrasound machines would list the studies scheduled in QualiScan (Modality Worklist), and the verified report would be delivered into your PACS as a PDF and into your RIS through the inbound interface your practice requests from its RIS vendor. It is designed to speak outward only, over HTTPS, to your own QualiScan deployment, with no inbound connection from the internet, and to listen only for your machines on their own network; it is designed to be managed and updated remotely.
Not live at any practice: scoped per practice before any commitment.
- 03Scoped per practice
Your RIS vendor’s inbound interface
Where your practice requests it from your RIS vendor, the verified report would be delivered into your RIS through the vendor’s own inbound interface, built only against your named RIS with its interface specification in hand.
Not built for any practice today: scoped per practice before any commitment.
How it fits today: QualiScan runs in the browser and covers worksheets, checks, report generation, verification and the billing export. The verified report is copied into your RIS, which stays the official record, or leaves as a PDF or a print. Your PACS stays the image archive of record. Where your practice switches it on, a read-only report API serves your other systems. QualiScan Connect, a connector at your site that would deliver into the PACS and the RIS, is in build and not live anywhere today.
Standalone today, nothing installedWorks alongside any RIS and PACSConnect and vendor interfaces scoped per practice
Open by design
Your reports, in formats other systems can read.
The QualiScan Open Report Format describes one ultrasound study: what the sonographer recorded, how the report reads, who signed it and when, and what happened to it after. Every worksheet field says how it came to be there: recorded by a practitioner, marked normal by an audited click, or not recorded. Nothing in a document’s structured members is computed, graded, scored or inferred, and the report text is your practice’s printed report, carried unchanged.
QualiScan Open Report Format
A documented, versioned JSON format for one ultrasound study, with a JSON Schema and a validator. Its licences are set: the format and its documentation under Creative Commons Attribution 4.0, the validator’s code under the Apache License 2.0. None of it is public yet, and the format is a draft.
HL7 FHIR R4
Through the report API, where your practice switches it on, each verified report as a Bundle: a DiagnosticReport with Observations for recorded fields only, patient identifiers exactly as recorded using the HL7 AU Base identifier systems, the radiologist as results interpreter and the PDF attached. Checked with the HL7 FHIR validator.
The PDF
The report exactly as your practice prints it.
A read-only report API
Versioned and documented inside the application, switched on per practice. Administrators create and revoke keys with read-only scopes; every request is logged against its key and rate-limited. Each verified report is available as a structured document, a FHIR Bundle and the PDF, with a feed of workflow events.
Signed notifications
Where your practice switches the report API on, webhooks tell your other systems when a report is sent, signed or amended, carrying identifiers and the event type only, never patient details.
The practice export
Where your practice switches the report archive on, an administrator can download, at any time, your worksheet catalogue and your verified reports for a chosen range of days, as structured documents in one archive, recorded in the audit trail.
Standard codes
LOINC codes for exam types and RSNA RadElement codes for fields and options, only where a code means exactly what the worksheet records. Everything else waits for review and is left uncoded rather than forced.
IHE MRRT templates
Example IHE MRRT report templates written from the standard worksheet structures: structure only, never your practice’s wording.
"fields": [
{
"label": "Length",
"kind": "measurement",
"unit": "cm",
"state": "recorded",
"value": 11
},
{
"label": "Corticomedullary differentiation",
"kind": "toggle",
"state": "marked_normal",
"value": "normal",
"markedNormal": { ... }
},
{
"label": "Hydronephrosis",
"kind": "select",
"state": "not_recorded"
}
]{
"resourceType": "Observation",
"code": { "text": "Right Kidney: Length" },
"valueQuantity": {
"value": 11,
"unit": "cm",
"system": "http://unitsofmeasure.org",
"code": "cm"
}
}A field that was not recorded has no Observation.
Demonstration data: excerpts, members left out
Ask us for the specification
The specification, its schemas and the validator are available to integration partners on request.
Billing
Billing, captured at the source.
- 01Capture
Billing details and the referrer are recorded with the study; where your practice sets billing rules, they are checked against them, as flags only.
- 02Review
A billing worklist of verified studies, with any flags beside each, ready to export.
- 03Export
A billing export for entry into your existing billing software.
- 04Claim
QualiScan makes no claim: claiming stays in your existing billing system, unchanged.
For Australian practices, Medicare stays in your existing billing workflow. New Zealand practices’ existing billing arrangements continue unchanged.
Roadmap
On the roadmap.
Listed apart from what ships today. None of these is live yet, and no dates are set.
- On the roadmap
Direct-to-GP delivery
Verified reports would travel to the referrer through secure messaging.
- On the roadmap
My Health Record upload
Upload of the verified report to My Health Record from QualiScan, for Australian practices.
Australian practices now share written diagnostic imaging reports with My Health Record by default. Your existing My Health Record arrangements continue through your RIS; QualiScan produces the verified report. New Zealand practices’ existing arrangements continue unchanged.
Subscription and data
A subscription that scales with your reporting.
No large upfront purchase and no heavy implementation project. QualiScan is a managed subscription that scales with the number of reports you generate each month, from a small clinic to a busy imaging centre. Hosting, updates, security and backups are handled for you: you always run the latest version.
Your practice owns its data, and QualiScan is verified for 100 reports a day per practice. For practices in Australia and New Zealand alike:
- Application servers and each practice’s database run in Sydney, with one dedicated database per practice and its own keys.
- Security headers and a content security policy on every page of the application.
- Encrypted off-provider backups of each practice’s database, scheduled every 6 hours, with a restore drill on record.
- Every submit, sign-off, amendment, acknowledgement, export and API key event in the audit trail.
- Role-based access for sonographers, radiologists and administrators, with no self sign-up: accounts are provisioned for your practice.
- An administrator can export the practice’s data at any time.
- No inbound connection from the internet: QualiScan Connect is designed to speak outward, over HTTPS, to your own QualiScan deployment, and to listen only for your machines on their own network.
- No shared database: one deployment per practice, with its own database and its own keys.
- No images leave the site unless the practice turns the image store on, and then only images the uploader confirms show no patient identifier.
- No AI in the reporting path: every sentence comes from a deterministic template, and every grade or category is selected by the practitioner, never computed.
- No Medicare claiming: billing items are captured and exported, and no claim is ever made from QualiScan.
Delivery of the finished report into a practice’s PACS and RIS is scoped per practice and not live anywhere today; reports leave today as PDF, print, copied text and the billing export.
FAQ
Questions, answered.
How does the subscription work?
QualiScan is a managed subscription that scales with the number of reports you generate each month, from a small clinic to a busy imaging centre. There is no large upfront purchase and no heavy implementation project.
Is QualiScan something we buy and install?
No. QualiScan is a managed service. Your practice subscribes and we run the platform: hosting, updates, security and backups are handled for you, so there is nothing to host or patch and you always run the latest version. Your practice owns its data. QualiScan’s application servers and each practice’s database run in Sydney, with one dedicated database per practice, and encrypted off-provider backups of each practice’s database are scheduled every 6 hours.
Can we get our data out?
Yes. Your practice owns its data, and an administrator can export it from the Administration page at any time. Where your practice switches the report archive on, an administrator can also download the worksheet catalogue and the verified reports for a chosen range of days as structured documents in the QualiScan Open Report Format, in one archive, and every download is recorded in the audit trail.
Where is our data hosted?
QualiScan’s application servers run in Sydney, and each practice has its own dedicated database in Sydney, with its own keys, for practices in Australia and New Zealand alike. Every page of the application carries security headers and a content security policy. Encrypted off-provider backups of each practice’s database are scheduled every 6 hours, and a restore drill is on record.
Do we need an integration to use QualiScan?
No. QualiScan is standalone by default and works alongside any RIS and PACS, with nothing installed and no changes to your machines, your PACS or your RIS. Sonographers fill structured worksheets in a browser, your radiologist verifies the report, and the verified report leaves as a PDF, a print, or a one-click copy of the report text with letterhead and referrer included.
Who moves the report into our RIS?
Your practice does, the same way a typed report is placed into the RIS today. One click copies the verified report text, letterhead and referrer included, and it is pasted into your RIS. Typing support is provided for that step, and your RIS stays the official record. Where a case combines QualiScan text with anything typed directly in the RIS, the QualiScan text goes in first and the additions follow.
Can QualiScan integrate with our RIS or PACS?
QualiScan is standalone by default. A connection into your PACS and RIS is scoped per practice before any commitment: QualiScan Connect, a small connector at your site, is in build, and delivery through your RIS vendor’s inbound interface would be built only against a named RIS with its interface specification in hand; neither is built for any practice today. Delivery of the finished report into a practice’s PACS and RIS is scoped per practice and not live anywhere today; reports leave today as PDF, print, copied text and the billing export.
What is QualiScan Connect, and is it live?
QualiScan Connect is a small connector at your site, one per site, and it is in build. Through it your ultrasound machines would list the studies scheduled in QualiScan, and the verified report would be delivered into your PACS as a PDF and into your RIS through the inbound interface your practice requests from its RIS vendor. It is designed to speak outward only, over HTTPS, to your own QualiScan deployment, with no inbound connection from the internet, to listen only for your machines on their own network, and to be managed and updated remotely. Delivery of the finished report into a practice’s PACS and RIS is scoped per practice and not live anywhere today; reports leave today as PDF, print, copied text and the billing export.
Is there an API?
Yes, where your practice switches it on: a read-only, versioned report API, documented inside the application. Administrators create and revoke keys with read-only scopes, and every request is logged against its key and rate-limited. Each verified report is available as a structured document in the QualiScan Open Report Format, as an HL7 FHIR R4 Bundle and as the PDF your practice prints, with a feed of workflow events. Signed notifications tell your other systems when a report is sent, signed or amended, carrying identifiers and the event type only, never patient details. An OpenAPI 3.1 description is available to integration partners on request.
Is the report format open?
The QualiScan Open Report Format is documented and versioned, with a JSON Schema and a validator, and its licences are set: the format and its documentation under Creative Commons Attribution 4.0, the validator’s code under the Apache License 2.0. None of it is public yet, and the format is a draft. Every worksheet field is recorded, marked normal by an audited click, or not recorded, and nothing in its structured members is computed, graded, scored or inferred. The specification, its schemas and the validator are available to integration partners on request.
How do images work?
Where your practice turns the image store on, sonographers attach reference images to a study, with a confirmation step, so your radiologist can view them while verifying the report. Your PACS remains the image archive of record.
Does QualiScan use AI?
No. There is no AI anywhere in the product. Reports are generated from deterministic templates, so the same input always produces the same words. Gradings, categories and recommendations are selected by your clinical team and verified by your radiologist, never computed by software.
Does QualiScan flag abnormal results?
No grading, category or level is ever computed: each is selected by your clinical team and verified by your radiologist. Measurements are recorded, and where a template shows a measurement against a reference range, that range carries its source and is never an invented threshold. The completeness and consistency checks say only what is missing or contradictory on a worksheet; they never say a finding is clinically wrong.
What about My Health Record?
Australian practices now share written diagnostic imaging reports with My Health Record by default. Your existing My Health Record arrangements continue through your RIS; QualiScan produces the verified report. Upload from QualiScan is on the roadmap, with no date set. New Zealand practices’ existing arrangements continue unchanged.
How does billing work?
Billing details and the referrer are recorded with each study, and QualiScan produces a billing export for entry into your existing billing workflow, which stays in your existing system; for Australian practices that includes Medicare. Where your practice sets billing rules, captured items are checked against them, as flags only. QualiScan makes no claim. New Zealand practices’ existing billing arrangements continue unchanged.
Can reports match our reporting style?
Yes. Reports are generated from deterministic templates in your radiologist’s own reporting style, tuned from their own sample reports, so the same input always produces the same words. Your radiologist can amend the generated text before sign-off, with the original preserved and the changes shown.
How do we trial QualiScan?
With a parallel run alongside your existing RIS, which stays the official record throughout. QualiScan is verified for 100 reports a day per practice.
Is QualiScan a medical device?
No. QualiScan is a workflow and reporting tool, not a medical device. A qualified radiologist verifies every report, and gradings and categories are selected by your clinical team, never computed. Demonstrations run on synthetic data only.
See a study go from worklist to verified report.
Open the demo. It runs on synthetic data only.