About the author

Jimenez Julien, the person behind MammoLoop

I write the software, I answer the support email, and I sit on the onboarding calls. If a recall wave goes out wrong, it is my name on it.

Portrait of Jimenez Julien

Why I built recall software for imaging centers

I did not come to breast imaging from medicine. I came to it from operations software, and from a long habit of asking small businesses which task they dread most on a Monday morning. When I started asking that question inside independent imaging centers, the answer was almost always the same, and it was almost always given by a woman with twenty years in the trade who had long since stopped expecting anyone to fix it. The recall list. The printout. The sixty calls.

What struck me was how badly the tooling matched the work. A radiology information system is very good at recording what happened during an exam. It is close to useless at answering the question a scheduler actually needs answered: which of the eleven thousand women who trusted us last year is due in the next sixty days, and which of them has already booked. Centers were bridging that gap with exports, highlighters and a legal pad, and they were losing patients in the gap. Not because anyone was careless, but because a person making calls between walk ins can only get through so many.

So I spent a year sitting with schedulers instead of writing code. I learned that the phone is the worst channel and the last one everybody defaults to. I learned that the letter track matters more than any software vendor wants to admit, because a sixty six year old woman with a landline and a mailbox is exactly the patient you cannot afford to lose. I learned that a no show is a fifteen minute problem if you catch it the same afternoon and a lost year if you catch it in next month's report. I learned that the callback log for short interval follow up is not an administrative detail, it is the thing a practice manager thinks about at two in the morning before an audit.

MammoLoop is the narrow product that came out of that year. It reads exam history, it maintains the annual due list, it sends staged texts and printed letters on a schedule you approve, and it hands your scheduler a short queue of the people who genuinely need a human voice. It does not read images. It does not touch reports. It does not try to become your RIS. Every time I have been tempted to widen the scope, someone running a center has talked me back out of it, and they have been right every time.

How I work with the centers who use it is simple and old fashioned. I do the onboarding call myself. I read the message templates out loud with the practice manager before a single text is sent, because copy written by a vendor sounds like a vendor and patients can tell. I ask for the baseline return rate before we start so that neither of us can be vague about the result later. When a center tells me a feature is missing, I ask which patient it lost them, and if the answer is concrete I build it. When the answer is not concrete, I say no, and I explain why.

What I am accountable for is narrow and specific: that the due list is correct, that no message goes to a patient who has already booked, that patient data stays inside the agreement we signed, and that a person answers when you write in. Those four things are the whole promise. Everything else on this site is detail.

Experience and expertise

  • Twelve years building operational software for small businesses that run on appointments and recurring visits.
  • Direct work with independent breast imaging centers, women's health practices and small multi site imaging groups across the United States.
  • Practical knowledge of HL7 order and result feeds, scheduled RIS exports and the messy record matching that follows a merger or a name change.
  • Working familiarity with HIPAA obligations for a business associate, business associate agreements, minimum necessary data and breach notification duties.
  • Hands on experience with high volume text messaging compliance, opt out handling and print and mail workflows including address correction and returned mail.

How this product is built and maintained

MammoLoop ships small changes often, and every change to messaging logic goes through a dry run against a copy of a real due list before it reaches a center. Nothing goes to patients from a test environment. Message and letter templates are versioned, so if a center asks what exactly was sent to a patient in March, the answer is on file rather than reconstructed.

Everything written on this site is written by me, checked against what the product actually does today, and corrected when it drifts. The numbers on the home page are medians from centers running the product for at least eighteen months, recalculated each quarter against their own baseline year. If a figure moves down, it gets edited down. Testimonials are published with the permission of the person named and are not edited beyond trimming length. Pricing on this page is the pricing you will be quoted.

Support is a real inbox, not a ticket maze. Email arrives with me. During onboarding I give you my direct line, and after go live the commitment is a reply inside one business day, which in practice is usually the same afternoon.

Contact the author

Write to jimenezjulien42@gmail.com with a question about recall, a request for a demo, or a correction to something on this site. Corrections are welcome and get answered first.

Request a recall review

Written and maintained by Jimenez Julien, who builds and runs MammoLoop day to day. Read about the author or write to him at jimenezjulien42@gmail.com.