A genetic test result can appear in a patient portal in seconds. Understanding it may take a conversation. Acting on it may take months.
A result may raise questions about cancer risk, reproductive choices, medication response, a child’s diagnosis, or relatives who may need testing. A negative result can still need context. A variant of uncertain significance can create anxiety without giving the patient a clear clinical answer.
That is why a released report is not the end of the patient journey.
It is the point when a different kind of work begins.
Someone needs to explain what the result does and does not mean. Someone needs to determine whether the patient needs counseling, a specialist referral, a family risk discussion, a care plan, or follow-up later. Someone needs to record what happened if the patient does not respond, declines counseling, changes providers, or receives an amended result.
That work is often split across genetic counselors, ordering providers, specialists, laboratory teams, schedulers, patient portals, EHR tasks, and clinical documentation systems.
The risk is not always that the result is wrong. The risk is that the result is clinically meaningful, but the next step disappears.
A genetic counseling follow-up workflow connects result delivery, post-test counseling, patient outreach, referrals, family discussions, care-plan actions, and recontact. It gives the program a clear record of what happened after the result was issued, what remains open, and who owns the next action.
The National Society of Genetic Counselors describes post-test counseling as helping patients understand a result and its implications for themselves and family members. It can include support resources, medical-management discussions, referrals, and follow-up planning. The NSGC Genetic Testing Resource outlines these responsibilities.
Explore connected genetic-testing workflows.
NonStop engineers systems that connect reporting, case management, patient and provider communication, counseling follow-up, and downstream clinical action.
A Released Report Is Not a Completed Patient Journey
A report status such as “released” or “delivered” answers a narrow technical question. It confirms that a document or result reached a destination.
It does not show whether:
- The patient understands the result.
- The ordering provider understands the next clinical step.
- Post-test counseling happened.
- A referral was accepted and completed.
- Family implications were discussed.
- At-risk relatives received appropriate information.
- The program has a plan if the result changes later.
The distinction matters for every type of genetic result.
A pathogenic or likely pathogenic result may lead to clinical management decisions, specialist referral, and family discussions. A negative result can still require residual-risk counseling based on family history. A VUS needs careful explanation because it does not establish a diagnosis or independently direct medical management. Carrier findings may require reproductive counseling. Pharmacogenomic results may need to reach a prescribing workflow.
For secondary findings in clinical exome and genome sequencing, ACMG’s 2021 policy states that pre-test and post-test genetic counseling should be provided to people receiving those findings. The counseling should address possible results, testing limitations, and medical implications. The ACMG 2021 secondary findings policy statement describes this expectation.
The report release is one event. It is not the care pathway.
The Follow-Up Work That Disappears Between the Lab and the Care Team
The work after result delivery is often invisible because it is distributed.
The lab may know when the report was released. The portal may know when the report was viewed. The counselor may know when a conversation happened. The EHR may hold a referral. The specialist may hold the treatment plan. A separate system may hold contact preferences or call attempts.
No one view shows the whole follow-up process.
| Follow-up event | What is usually recorded | What is often missing |
|---|---|---|
| Report released | Report version, date, delivery destination | Whether patient follow-up was needed |
| Portal opened | Document-view or login event | Whether the patient understood the result |
| Counseling scheduled | Appointment date | Whether the session happened and what actions followed |
| Counseling completed | Note, encounter, or task closure | Whether referrals, care-plan tasks, or family follow-up occurred |
| Referral placed | Referral order | Whether the referral was scheduled, completed, declined, or lost |
| Family discussion documented | Note or counseling summary | Whether eligible relatives received resources or testing support |
| Report amended | New report version | Whether the patient, provider, and counselor were contacted again |
This is where follow-up becomes a case-management problem.
A patient may appear “complete” in the laboratory system while still having open work across counseling, referral, family follow-up, or recontact.
Patient Acknowledgment Is Not Patient Understanding
A portal-view event is useful. It is not proof of understanding.
A patient may open the report before anyone has explained it. The patient may read only the result summary. The patient may not understand the limits of a negative result. The patient may interpret a VUS as a diagnosis. The patient may not realize that relatives could be affected.
A patient acknowledgment workflow needs clear definitions.
| Signal | What it confirms | What it does not confirm |
|---|---|---|
| Portal opened | The report page was viewed | The result was understood |
| Message sent | Outreach was attempted | The patient received or acted on it |
| Counseling appointment booked | A future session is planned | Counseling occurred |
| Counseling note completed | An interaction was documented | Every referral or family action is complete |
| Patient acknowledgment captured | The patient confirmed receipt or a specific action | The full care pathway is complete |
| Referral order created | A referral was initiated | The patient attended the specialist visit |
This is not an argument for turning every patient interaction into a rigid workflow.
It is an argument for separating what the program knows from what it assumes.
The system should not infer that a portal view equals counseling completion. It should not infer that a referral order equals clinical follow-up. It should not close a case because a report was delivered.
Connect reports to follow-up work.
NonStop designs systems that connect diagnostic reports, patient and provider communication, EHR tasks, referrals, care plans, and case ownership.
Different Results Create Different Follow-Up Paths
A genetic counseling program should not manage every result through the same queue.
The result category, clinical context, patient preference, family history, care setting, and applicable policy determine the next steps.
| Result category | Follow-up focus | Example workflow actions |
|---|---|---|
| Pathogenic or likely pathogenic | Clinical implications, specialist referral, family risk, counseling | Assign counselor, document discussion, create referral tasks, record family follow-up |
| Negative | Residual risk and testing limitations | Document result context, explain limits, note any future testing or surveillance discussion |
| VUS | Uncertainty, non-diagnostic status, reanalysis expectations | Document patient education, preserve recontact status, avoid unsupported treatment actions |
| Carrier result | Reproductive implications and partner-testing discussion | Offer counseling, record partner-testing decision, route referral if needed |
| Pharmacogenomic finding | Medication relevance and provider workflow | Deliver structured result, route provider action, track decision-support follow-up |
| Amended or reclassified result | New evidence and potential clinical impact | Trigger clinical review, update report, contact patient and provider according to policy |
The clinical policy behind these actions belongs to the medical director, genetic counseling leadership, treating clinicians, and the organization’s governance process.
NonStop engineers the systems that make approved workflows visible and operational.
VUS results show why this matters. A peer-reviewed study of genetic counselors found that VUS disclosure can create challenges for both patients and counselors. The study emphasized the need for personalized post-test counseling and discussion of implications for family members. The study in the Journal of Genetic Counseling describes the practical complexity of VUS communication.
A Counseling Program Needs to Manage Open Work
Scheduling is necessary. It is not case management.
A counseling team needs visibility into work that is still open:
- Results awaiting patient outreach.
- Patients who need a counseling session.
- Appointments that were missed or declined.
- Referrals that remain incomplete.
- Cases with family-risk discussions pending.
- Patients who need written resources.
- Amended reports that require recontact.
- Cases where the ordering provider has not acknowledged the result.
- Time-sensitive cases that need escalation.
A useful counseling queue shows more than appointments.
It shows the clinical and operational status of each case.
| Queue field | Why it matters |
|---|---|
| Result category | Determines the likely urgency and follow-up path |
| Report version | Ensures the team works from the current clinical record |
| Counseling status | Separates needed, scheduled, completed, declined, and unreachable cases |
| Patient communication status | Shows whether outreach was attempted and what happened |
| Referral status | Tracks recommended, ordered, scheduled, completed, or declined referral activity |
| Family follow-up status | Documents whether family implications and cascade testing were discussed |
| Recontact flag | Identifies cases that may need future outreach |
| Owner and due date | Makes responsibility visible |
| Open task age | Identifies cases at risk of being lost |
This type of workflow does not replace clinical judgment. It gives the counseling program a reliable way to act on that judgment.
Referrals and Family Follow-Up Need a Closure State
A referral is not complete when it is placed.
A cascade-testing conversation is not complete when it is documented.
Programs need a way to track the work they own without attempting to control a patient’s decisions or a relative’s care.
- Needed
- scheduled
- completed
- declined
- no-show
- closed
- Recommended
- ordered
- scheduled
- completed
- declined or unreachable
- Discussed
- resources requested
- resources sent
- follow-up pending
- closed
- Eligible relative identified
- information provided
- test requested
- result available
- follow-up complete
- Trigger identified
- clinical review
- patient outreach
- discussion complete
- documentation finalized
These are not universal states. Each organization needs to define what it can responsibly track.
The purpose is to prevent a clinically important next step from becoming a note that no one revisits.
ACMG secondary-finding recommendations state that the ordering clinician or team is responsible for comprehensive pre-test and post-test counseling. They also describe the need for medical follow-up and appropriate involvement of clinical genetics expertise given the complexity of genomic information. The ACMG recommendations for incidental findings describe those care responsibilities.
When a Result Changes, the Follow-Up Workflow Starts Again
Genetic information is not static.
A report may be amended because a variant classification changes, a laboratory corrects an error, new evidence affects interpretation, or an updated report becomes clinically relevant.
A recontact workflow needs more than a new PDF.
It needs to answer:
- Which version of the report was previously issued?
- Who received it?
- Which provider is currently responsible for care?
- Is the patient reachable and eligible for outreach?
- Does the change require genetic counselor review?
- Does the patient need a new discussion, referral, or care-plan action?
- What outreach attempts occurred?
- When is the case closed?
FHIR provides useful resources for representing this kind of connected workflow.
- DiagnosticReport can represent the released diagnostic report.
- Task can represent an assigned action.
- CarePlan can represent a plan of care.
- FamilyMemberHistory can preserve relevant family data. The HL7 FHIR R4 specification defines these resources and their use across clinical workflows.
The technical model does not decide whether or when recontact is clinically required. That decision belongs to the organization’s approved policy and clinical governance.
The system records the trigger, owner, actions, evidence, and closure.
The Minimum Follow-Up Record for a Genetic Testing Program
A follow-up workflow becomes manageable when the program has one record that shows the patient’s open work.
| Record element | What it answers |
|---|---|
| Patient, order, accession, and report IDs | Which case is this? |
| Current report version and result category | What information is active? |
| Ordering provider and care team | Who needs visibility or action? |
| Result-delivery status | Did the report reach the intended destination? |
| Counseling status | Was counseling needed, scheduled, completed, declined or unresolved? |
| Patient communication history | What outreach occurred, and what was the outcome? |
| Referrals and care-plan tasks | What clinical follow-up remains open? |
| Family discussion and cascade-testing status | Were family implications addressed? |
| Recontact eligibility and trigger | Does the program need to revisit the result later? |
| Case owner and due date | Who is responsible for the next action? |
| Closure evidence | Why is this case considered complete? |
This record does not need to live in a new application. It does need to be governed.
The program must know which system owns each field, how updates flow between systems, and where staff can see open work without searching across multiple tools.
The Work That Needs a Named Owner
A genetic result can change a patient’s understanding of their health, their family, and their options.
The laboratory report is essential. It is not sufficient.
The work after result delivery needs a named owner, a visible status, a documented next action, and a closure record.
NonStop engineers the systems that connect genetic test reporting, case management, counseling worklists, provider and patient communication, referrals, care plans, and recontact workflows.
NonStop designs workflow layers that preserve report versions, task ownership, audit trails, and cross-system case identity. NonStop also integrates clinical workflows through HL7 v2, FHIR R4, EHR integration, patient and provider experiences, and reporting systems. Explore NonStop’s genomics infrastructure and integration engineering.
Build a Genetic Counseling Follow-Up Workflow That Keeps Open Work Visible
NonStop’s 45-minute Architecture Review maps the workflow that begins after a genetic test result is released.
The review identifies:
- Results with no documented patient outreach or counseling status
- Referrals and care-plan tasks without closed-loop tracking
- Family and cascade-testing discussions that rely on manual follow-up
- Amended-result and recontact workflows that lack ownership
- Gaps between the lab report, patient portal, EHR, counseling queue, and clinical follow-up systems
- The case-management, reporting, and integration changes needed to establish a governed follow-up record
For an initial discussion about the current workflow:
Book a 15-Minute Scoping CallFrequently Asked Questions About Genetic Counseling Follow-Up Workflows
What is a genetic counseling follow-up workflow?
A genetic counseling follow-up workflow manages the work that occurs after a genetic result is released.
It connects patient outreach, counseling, provider communication, referrals, care plans, family discussions, cascade testing, and recontact. It makes the next action visible and assigns it to a responsible owner.
Does a delivered result mean the follow-up is complete?
No.
A delivered result confirms that a report reached a destination. It does not confirm that the patient understands the result, received counseling, completed a referral, or discussed family implications.
What should a genetic counseling case record include?
A case record should include patient, order, accession, and report identifiers. It should also include result category, report version, counseling status, communication history, referrals, care-plan tasks, family follow-up, recontact triggers, owners, due dates, and closure evidence.
How should a program handle VUS follow-up?
A VUS should be explained as a finding that does not establish a diagnosis or independently direct medical management. The program should document counseling, patient education, clinical context, and recontact or reanalysis status according to approved policy.
How can a program track referrals after results are delivered?
The system should track referral status from recommendation through order, scheduling, completion, decline or unsuccessful outreach. A referral order does not prove that the patient received follow-up care.
What is genetic recontact?
Genetic recontact is the process of reaching a patient or provider when new information may materially affect a previously issued result. It requires a trigger, clinical review, report version control, outreach tasks, documented communication, and closure criteria.

