Get started
ClinicalLive · in the productClinical record

HysteroscopyLog

Every hysteroscopy, with what the scope saw set against what the ultrasound predicted.

What it is

For gynaecology teams who scope. Each hysteroscopy — diagnostic or operative, in the office or in theatre — is recorded with its indication, what was done and any complication, and two lists from the same short set of findings (polyp, submucous fibroid, septum, adhesions, retained products, a device, abnormal-looking endometrium, or a normal cavity): what the ultrasound report before it predicted, with the scan’s date, and what the scope saw. Agreement is counted per finding over the last year — predicted and seen, predicted but not seen, seen but not predicted — so the team can see how often the scope confirms the scan. Nothing advises when to scope; the counts are for your team to read. A specimen sent stays on the list until the pathologist’s result is entered, once. The record is kept as written; a correction is a dated addendum.

Who uses it
Built for: Obstetrics & Gynaecology · ivf-fertility
Reads
The patient record, the pre-operative ultrasound report
Writes
Hysteroscopy records, histology results, scan–scope agreement
Never
It does not read the ultrasound images or decide who needs a hysteroscopy.
Access
Only people whose role includes it — the clinic owner decides who
Your data
Full PHI. Hosted in Boston, United States. On uninstall: Recording stops; every hysteroscopy and its histology stay on the patient’s record.

In the product

Who uses it
Doctor — the demo profile it is best tried as
Where it opens
Clinical › Hysteroscopy log /hysteroscopy
Permission
hysteroscopy.read
Every clinical app in the handbook →

How it works

  1. Record the procedureDiagnostic or operative, office or theatre.
  2. Tick the scan’s predictionFrom the report, with its date.
  3. Tick what the scope sawFrom the same list.
  4. Enter the histologyOnce, as the pathologist reported it.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It does not read the ultrasound images or decide who needs a hysteroscopy.
It records what the report predicted and what the scope saw.

AI in HysteroscopyLog

AskQuestions about what is on screen — “What needs attention in HysteroscopyLog today?” — answered with the records it read.
DraftSummaries and notes for the team, marked as drafts until a person signs.
Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

Live product
01Hysteroscopy log — Log every hysteroscopy against the scan before it and chase the histologyCaptured from the running demo clinic
HysteroscopyLog — Hysteroscopy log — Log every hysteroscopy against the scan before it and chase the histology
1 of 1

Connected to

Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.

Reads from · 1
See the whole clinic →

Questions clinics ask

What does HysteroscopyLog do?
Every hysteroscopy, with what the scope saw set against what the ultrasound predicted. For gynaecology teams who scope. Each hysteroscopy — diagnostic or operative, in the office or in theatre — is recorded with its indication, what was done and any complication, and two lists from the same short set of findings (polyp, submucous fibroid, septum, adhesions, retained products, a device, abnormal-looking endometrium, or a normal cavity): what the ultrasound report before it predicted, with the scan’s date, and what the scope saw. Agreement is counted per finding over the last year — predicted and seen, predicted but not seen, seen but not predicted — so the team can see how often the scope confirms the scan. Nothing advises when to scope; the counts are for your team to read. A specimen sent stays on the list until the pathologist’s result is entered, once. The record is kept as written; a correction is a dated addendum.
What data does HysteroscopyLog read and write?
HysteroscopyLog reads the patient record, the pre-operative ultrasound report and writes hysteroscopy records, histology results, scan–scope agreement. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.
What does HysteroscopyLog deliberately not do?
It does not read the ultrasound images or decide who needs a hysteroscopy. It records what the report predicted and what the scope saw.
What happens to our data if we uninstall HysteroscopyLog?
Recording stops; every hysteroscopy and its histology stay on the patient’s record.
Is HysteroscopyLog available today?
Yes — HysteroscopyLog is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see HysteroscopyLog running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

We use your name, phone number and clinic name for one thing: to answer this enquiry about MedAppz. It is stored on our own server, in the single region our trust centre names, and it is not sold or passed to anyone else.

Email us

You can withdraw either at any time: write to hello@medappz.com, or tell whoever calls you, and we will delete what you gave us.

More in Clinical

All 215 →