Skip to main content

Practice Operations

Genetic Counseling Referral Intake Starts With the Form

Genetic counseling referral intake stalls on a family history form that nobody chased. Here is how AI completes the packet before the visit is booked.

7 min read

Genetic counseling referral intake runs backwards compared to almost every other specialty. In most practices the appointment comes first and the paperwork catches up. Here the paperwork is the appointment. A visit booked without a completed family history is a visit that will get most of the way through and then stop.

A genetics referral arrives as a fax or a portal order with a reason attached, and almost never with what the visit actually requires. The family history questionnaire is missing. The pathology report referenced in the referral is not attached. Prior testing was done somewhere else and nobody has the result. Insurance is on the referral but the plan on file is a year old.

Each of those is a phone call to a different party, and none of them can start until somebody reads the referral closely enough to notice what is absent. In a small genetics practice, that somebody is also the person doing everything else.

So referrals sit. The queue is not a backlog of work, it is a backlog of unstarted phone calls, and every day one sits is a day added to a wait time that is already the practice’s biggest complaint.

The family history is a data collection project

Start with what the form is. A family health history is a record of health conditions among close relatives, and public health guidance treats gathering one as an active collection task rather than a question with a short answer.

That is why handing a patient a questionnaire and hoping produces the results it does. The patient does not have their aunt’s health details on hand. They have to call their mother, who has to call her sister. Getting a usable history is a multi-day errand that happens in the patient’s family, not in your office.

Which makes the timing the whole game. A form issued at booking and chased twice has weeks to complete. A form handed over at check-in has minutes and will not. The automation issues it the moment the referral is logged, confirms receipt, and follows up on a schedule rather than when someone notices, and it does that in whatever channel the patient actually answers.

Chase the referring office, not just the patient

Half of what is missing was never the patient’s to supply. Prior test results, the pathology report, imaging, and the specific indication live at the referring practice, and that office is not going to send them unprompted.

This is a solved pattern in other specialties. One practice asked whether the system could notice that labs or imaging referenced on an inbound referral were missing and automatically call the referring office to request them. That is exactly the shape here, with the added wrinkle that in genetics the missing item is often prior testing done at a third lab entirely.

athenaOne holds the surfaces this runs on. Referral orders and referral sources are readable, so the automation knows who sent it and can route the request back to them, and the outbound request lands as a generated document attached to a fax rather than a note asking someone to make a call later.

The form has to belong to the appointment type

There is a configuration detail here that separates practices where this works from practices where it does not.

Forms and consents need to be linked to the appointment type rather than issued as a generic intake packet. One practice specifically wanted the right consents to attach automatically to an office procedure type, and flagged that intake was the one document that did not make it into the chart reliably.

In genetics the same principle carries more weight because the packet varies. A cancer genetics evaluation, a prenatal consultation, and a pediatric evaluation need different histories and different consents. If the automation issues one generic packet, staff spend the saved time deleting what does not apply and hunting for what is missing.

Some fields also stay manual on purpose. In one form-automation build, demographics auto-filled while race, ethnicity, and insurance were deliberately left for a person. That was a judgment call about where automation should stop, and it is the right kind of call to make explicitly rather than by default.

Completeness gates the booking, so make the gate visible

If a complete packet is what makes the visit work, then packet state belongs on the schedule rather than in someone’s head.

The useful version of this tracks every referral as a small set of conditions: history received, prior results received, insurance verified, consent signed. A referral is bookable when those are true and visible as incomplete when they are not. The practice stops discovering a gap on the morning of the visit.

Minimum lead time is the lever that makes it work. Practices commonly hold new patients out of the next few business days precisely so intake can be completed, while established patients can book much sooner. That rule exists to protect exactly this workflow, and enforcing it at the moment a date is offered turns a policy into a constraint.

The payoff is a shorter effective wait, not a longer one. Visits that would have been rescheduled for an incomplete packet stop being scheduled twice, and the slots those consumed go to patients who are ready.

Where it stops

The automation collects, chases, and files. It does not evaluate what it collected.

It does not decide whether a referral is appropriate for genetics, does not read a family history to judge whether a patient meets criteria, does not determine urgency, and does not interpret a pathology report or a prior test result. Every one of those is a clinician’s call, and the completed packet exists to put it in front of them faster.

The handoffs are specific. A referral whose indication is unclear goes to your genetic counselor to scope. A patient who describes symptoms during a form-completion call goes to clinical staff immediately. A prior result that arrives and appears to conflict with the referral goes to a person, because reconciling those is interpretation.

What is left for the automation is the part that was always administrative: getting every document that the visit needs into the chart before the visit happens.

Key Takeaways

  • Issue the family history questionnaire at referral logging rather than at check-in, because completing one is a multi-day errand inside the patient’s family.
  • Chase the referring office directly for prior results and reports, since those were never the patient’s to supply.
  • Link forms and consents to the appointment type so a cancer, prenatal, or pediatric evaluation gets the packet it actually needs.
  • Track packet completeness as a visible booking condition instead of discovering the gap on the morning of the visit.
  • Enforce the new-patient minimum lead time at the moment a date is offered, since that rule exists to protect intake.

Genetic counseling referral intake is a document-completion problem that presents as a scheduling problem. Issue the history early and chase it on a schedule, request prior results from the office that has them, attach the right packet to the right visit type, and make completeness a condition of booking. The wait gets shorter because fewer visits have to happen twice.

Sources

Ready to See It in Action?

See how PGA completes referral packets before the appointment inside athenaOne

Schedule a Demo →

Written by Kevin Henrikson