Bug #712
openFertility Department Needs a Couple-Level Consultation Screen
100%
Description
Summary
In the Fertility/IVF department, consultations currently appear to use the standard individual-patient consultation screen, with the husband and the wife registered and consulted as two separate, unrelated patients. The ask is for a dedicated consultation screen for Fertility that treats the couple as one unit — their history, investigations and treatment plan tracked and viewed together, rather than as two disconnected patient journeys.
Impact
Fertility/IVF treatment is inherently couple-based: diagnosis, investigations (e.g. semen analysis for the husband, ovarian reserve/hormonal workup for the wife) and treatment cycle decisions depend on both partners’ combined clinical picture. Treating them as entirely separate patients makes it hard for the doctor to see the full couple’s history in one place during a consultation, increases the risk of fragmented or missed information, and adds manual work cross-referencing two separate records every visit.
Environment
Clinq HMS, Fertility/IVF department consultation workflow. Reported by description; not yet tied to a specific tenant or screen with a live walkthrough.
Steps to Reproduce
Current behavior (not a crash, a design gap): 1. Register a husband and wife as two separate OPD patients under the Fertility/IVF department.
2. Open a consultation for either one.
3. The consultation screen shows only that individual’s own demographics, history and investigations — there is no way to view or manage both partners together as a couple from one screen.
Expected vs Actual
Expected: Fertility department should have a dedicated consultation screen that treats a husband and wife (couple) as one linked unit — a single consultation view showing both partners’ demographics, history, investigations and treatment plan together, instead of requiring the doctor to open and cross-reference two separate individual patient records.
Actual: Husband and wife are each currently handled as fully independent patients, with no couple-level linkage or combined consultation view.
Notes
This is an enhancement/design request rather than a defect — the system is not failing to do something it was built to do; it currently handles every patient individually by design, and couple-level handling for Fertility does not appear to exist yet. Flagging this since it’s a gap rather than broken behavior.
RH Updated by Roshni Harish. 10 days ago
- Priority changed from Normal to Urgent
S- Updated by SK - 4 days ago
Triaged (2026-11-09), not resolved - confirmed genuinely unbuilt. Checked opd/emr/ipd/admin/clinq-docs against origin/dev: no couple/partner-linked entity, no IVF-cockpit component. The only existing link entity, PersonPatientLink (nuvita-emr), is a 1:1 identity-dedup link for merging duplicate records of the SAME person, not for linking two different people as a couple. clinq-docs/modules/opd/data-model.md:227 explicitly says Fertility is "deferred to a follow-on spec." Fertility exists today only as a department master-data row and a disabled "Fertility (coming soon)" tab (register-imports page).
This clusters with #713 (same root ask, generalized: rework consultation per department) and #687 (Fertility has no doctor assignment or any consultation tab at all - same underlying gap, reported Urgent). #654 (Fertility Scan form) is blocked on this cluster - can't add a Fertility exam form with no Fertility tab to put it in.
Parked per the user's call, to be scoped together with #695, #713, #687, #654 via a proper brainstorm/spec session (clinq-docs design workflow) rather than piecemeal. Left assigned to SK, status unchanged.
S- Updated by SK - 3 days ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
- Resolved By set to SK -
Implemented and merged to dev across all four repos (2026-11-10):
- nuvita-emr: new PatientPartnerLink entity + PatientPartnerLinkParticipant table (enforces at most one active link per patient, race-safe under concurrent linking), PatientPartnerLinkService, PatientPartnerLinksController (link/get-partner/unlink).
- nuvita-admin: emr.patient_partner_links.{create,read,delete} permission keys seeded (create/read to Doctor, Visiting Consultant, Receptionist, Nursing Lead, Hospital Administrator; delete clinical-only).
- nuvita-opd: registration screen gets an optional "Partner" section for Fertility-department walk-ins (search existing patient or quick-register one, link fires once the new patient's own registration succeeds); Fertility consultation tab gets a Partner card (Link/Unlink, with confirmation before unlinking), a semen-analysis entry form (6 fixed fields, always attributed to whichever partner is Male regardless of which chart it's entered from) and a Partner summary card showing the linked partner's latest semen-analysis values alongside the current patient's.
- Design: husband and wife stay two separate real patients (not merged into one chart) - linked via the new PatientPartnerLink, so each keeps their own longitudinal record while the Fertility tab cross-references both. Spec: clinq-docs/modules/emr/specs/2026-11-09-fertility-partner-linking-design.md.
QA change log entry: clinq-docs/shared/release-notes/qa-change-log.md, "OPD - new: linking a Fertility patient to their partner (Redmine #712)" - has the full Check list and deploy gates (2 new EMR migrations to run per tenant, --reseed-roles for the new permission keys, OPD's own API must be redeployed after EMR since it hosts EMR's controllers in-process).
Two related gaps found during final review were deliberately NOT fixed here (filed separately rather than risking a late design change) - see the two new tickets linked below:
- Patient merge doesn't repoint an active partner link.
- The quick-register "find or register a partner" dialog skips the usual duplicate-patient check and can create an orphan/duplicate patient record in some flows.
Not yet deployed to any tenant - pending migrations + role reseed per the QA log's deploy gates.
S- Updated by SK - 1 day ago
- Assignee changed from SK - to Roshni Harish.
Reassigning to Roshni for verification. Confirmed shipped: PartnerLinkControl, the shared partner search/create dialog, Fertility walk-in registration's Partner section, and SemenAnalysisEntry are all on dev (nuvita-opd, nuvita-emr), with a QA change-log row already in place.