TL;DR
Transfer open fertility inquiries as accountable administrative work, with recipient-specific contact restrictions. A shared family-building inquiry must not turn every listed person into a promotional contact. Require a minimum-data continuity export that preserves the authorized recipient, unresolved question and accepted practice owner, then test ambiguous and conflicting preferences before the new workflow sends anything.
Transfer responsibility for the open request
A shared inquiry may list an intended parent and another person, use a shared contact route or ask that replies go only to the original sender. These are conditional administrative examples, not assumptions about every family. When agencies change, a flattened contact list can lose the distinction between the person who asked and someone merely mentioned.
The practice needs to know what it still owes and to whom an approved response may go. An agency does not need clinical narratives, reproductive histories or assumptions about family roles to preserve that administrative responsibility.
Use the general agency-exit rehearsal for export terms, public destinations and account dependencies. This fertility handoff adds a specific acceptance condition: participants and their preferences must survive without becoming interchangeable recipients.
Specify a minimum-data continuity export
Minimum means sufficient for the approved continuity task, not a universal legal field list. Have the practice's responsible reviewers decide actual access, permitted transfer and retention. Keep underlying sensitive records in approved systems; references below do not authorize disclosing their contents to an agency.
| Continuity field | What the receiving practice needs | Unacceptable substitution |
|---|---|---|
| Open inquiry reference | Approved operational reference linking the pending request | A bulk clinical record export |
| Recipient role | Who actually requested the response, or unresolved status | An assumed recipient based on family relationship |
| Approved contact route | Current permitted destination, channel and restrictions | Every address listed on the inquiry enrolled by default |
| Preference evidence reference | Source and current meaning of the restriction in the approved system | A new-contact label that discards prior preferences |
| Unresolved administrative question | Scheduling, fee-process, referral-receipt or other approved category | Clinical details copied to make a marketing note more complete |
| Practice action owner | Named receiving role and accepted next task | Outgoing vendor listed after access ends |
| Pending message state | Task purpose and hold or cancellation state | Old promotional work silently recreated on import |
| Inquiry origin | Original receipt cohort and supported source | Transfer date rewritten as acquisition date |
| Missing or conflicting evidence | Explicit gap and responsible resolver | Guessed permission or a guessed relationship |
Ask the receiving operator to interpret the export without the old interface. If a field such as “primary contact” has no clear meaning, document it before import. It might identify a billing role, original sender or software default; none should silently become permission for promotional contact.
Resolve recipient ambiguity inside the practice
Keep person-specific preferences separate even when people share a contact route. Do not infer that a change requested by someone on a shared inquiry resolves every participant's preference. Have the responsible practice team determine the actual approved recipient and use through its established process.
Do not let deduplication by a shared email address or phone number erase participant roles or conflicting restrictions. Preserve the links between the inquiry, the requested task and its approved recipient. If the destination's meaning is unresolved, keep the affected sending task held while the practice resolves it; a successful contact merge is not acceptance evidence.
For U.S. HIPAA-regulated uses of protected health information, marketing generally requires written authorization, subject to limited exceptions and defined distinctions. HHS marketing guidance and the current authorization rule provide the relevant framework.
The practice's qualified reviewers must assess the actual information, purpose, recipient, channel and jurisdiction, including other applicable rules. Technical exportability and contract access do not settle permitted contact. Preserve restrictions while unresolved outreach remains on hold; necessary practice work should follow its separately approved process.
Rehearse the shared-inquiry failure
Use clearly labeled synthetic records in a controlled setup with no real outreach or appointments. Create an open administrative question, a specified recipient, another listed participant and a restriction affecting the response route. Include a queued promotional task that should remain held under the approved test policy.
Have the receiving team demonstrate the following acceptance conditions. These are test specifications, not findings about an actual system.
| Test condition | Evidence to require |
|---|---|
| Another person is listed on the inquiry | Import does not create promotional enrollment for that person |
| Shared destination has ambiguous permission evidence | Sending remains held while the responsible practice owner resolves it |
| A shared address appears under different participant roles with conflicting restrictions | Import preserves the role links and conflict; no merged record gains active sending status by default |
| The original sender requested a pause | Restriction survives import and applies to pending promotional work |
| An administrative answer is still owed | Receiving practice role accepts the task without guessing a new recipient |
| A later scheduling event is added | Original inquiry cohort remains intact |
| An export field is missing | Gap remains explicit instead of being converted into active permission |
Record failed field mappings, obsolete tasks and unaccepted responsibilities precisely. Repair and repeat the affected test. Do not accept an import merely because the total number of rows matches.
Keep continuity separate from the cohort report
A cohort report describes acquisition evidence and the states visible at its cutoff. This handoff establishes who receives open work and how recipient restrictions survive a vendor boundary. Retaining a cohort does not answer those questions.
If the actual consultation offer changed, operations must verify and explain the current arrangement through the approved practice process. Keep the continuity export focused on accepted tasks and who may receive the response; a historical offer does not settle current availability.
Use the agency data-request review to challenge unnecessary fields. Accept the continuity package only when its actual evidence, exclusions, open tasks and receiving owners are documented. GetPatients has a commercial interest in healthcare visibility services; these requirements apply to its proposals too.
Frequently asked questions
Can every person listed on an inquiry receive the new agency's messages?
Do not assume that. Preserve recipient-specific evidence and have the practice determine permitted communication before enrollment.
What if the export lacks preference history?
Keep the gap explicit and hold affected promotional outreach. Seek a permitted interpretable alternative while the practice continues necessary work through its approved process.
Does preserving the original inquiry cohort complete the handoff?
No. The receiving practice must also accept the unresolved task and interpret recipient and contact restrictions. Historical reporting and operational continuity require different acceptance evidence.