Confidential mandate
Fertility-Care Journey Architect
Planned Hiring / New
Fertility-Care Journey Architect mandate in Barcelona, Spain · Fertility Treatment Networks
A multi-country fertility group needs an operating architecture that connects referral, diagnostics, consent, treatment scheduling, laboratory capacity and emotional support without standardising clinical judgment after rapid expansion.
The mandate
The group’s clinics have grown through acquisition, leaving different definitions for enquiry, diagnostic readiness, consent completion, cycle start and post-treatment closure. Scheduling teams promise dates before medication, laboratory and patient dependencies align; people repeat histories across borders; and emotionally difficult pauses disappear from throughput reports. The defined problem is to create one care-journey operating model that makes handoffs and capacity dependable without imposing uniform clinical choices.
The principal deliverable is a Fertility-Care Journey Architecture covering first contact, eligibility routing, diagnostics, clinical plan handoff, consent, financial authorisation, medication readiness, theatre and laboratory scheduling, sample custody interfaces, cycle change, cancellation, result communication, counselling, onward care and record closure. It will include journey states, clinic archetypes, decision rights, minimum evidence, capacity rules, privacy boundaries, exception pathways, service measures and implementation sequencing.
Four milestones govern five months. By week four, milestone one reconstructs thirty de-identified journeys across eight clinics. Week nine delivers state, demand and capacity baselines with failure themes. Week fifteen completes design laboratories and simulations for donor delay, laboratory constraint, consent withdrawal, cross-border transfer and failed cycle. At week twenty, the final milestone supplies the accepted architecture, eight clinic transition plans, workforce implications, system requirements and mobilisation backlog.
Acceptance rests jointly with the chief operating officer and Clinical Governance Council, with clinicians, embryologists and privacy officers approving professional boundaries. Work is accepted only when two country teams can move five unseen scenarios through named owners, capacity and consent states reconcile, patients receive coherent communication, and no operational measure infers success from treatment outcome. Sample and embryo custody interfaces must remain attributable to authorised laboratory systems and professionals.
The client provides de-identified journeys, clinic schedules, capacity, consent frameworks, handoff records, complaints, patient research permissions, system states and controlled observation access. Consultants will not advise patients, determine eligibility, design treatment, interpret diagnostics, handle samples, assess embryo quality or change clinical protocols. Technology build, medical outcome analysis, payer negotiation and live implementation are excluded; missing clinical evidence remains a named dependency.
Why this is external work
Country and clinical teams rightly defend local practice, while central operations needs comparability and acquisition value. Prior standardisation attempts started with systems rather than patient and professional decision boundaries. External architecture brings neutral journey reconstruction, cross-clinic capacity design and acceptance testing without assuming any clinical or laboratory authority.
What you will own
- Reconstruct thirty journeys from enquiry through diagnostics, consent, scheduling, laboratory handoff, outcome communication and closure, including pauses, transfers and failed cycles.
- Define shared journey states while preserving legitimate clinical, donor, legal and country differences.
- Map decision rights across patient services, clinicians, nursing, embryology, counselling, finance and country operations.
- Build capacity rules joining consultation, diagnostics, theatre, laboratory, medication, donor and support constraints.
- Exercise donor delay, consent withdrawal, laboratory constraint, cross-border transfer and failed-cycle scenarios.
- Specify evidence, privacy, communication, exception and escalation requirements for each clinic archetype.
- Deliver the accepted architecture, eight transition plans, system requirements and sequenced mobilisation backlog.
Candidate qualifications
- Has designed operating models across fertility, reproductive health or another emotionally and clinically complex care network with laboratory, counselling and cross-border dependencies.
- Can evidence a scheduling redesign that respected consent, laboratory capacity and professional judgment.
- Understands diagnostics, treatment planning, medication, theatre, embryology, donor pathways, counselling and privacy interfaces.
- Has integrated acquired clinics without erasing legitimate clinical and jurisdictional variation.
- Can separate patient experience and operational closure from clinical outcome or pregnancy-rate inference.
- Has facilitated clinicians, laboratory leaders, operations and patient representatives through controlled pathway acceptance.
Non-negotiables
- Can complete eight clinic observations and two cross-country simulations within five months.
- Will not provide care, interpret results, determine treatment, handle samples or judge embryo quality.
- Brings direct clinically governed journey architecture; generic healthcare customer experience is insufficient.
- Will preserve paused, cancelled, transferred and emotionally difficult journeys in service evidence.
- 49 words maximum. Which fertility or clinical journey state most often creates a false view of capacity?
- 49 words maximum. Describe an operating change that protected consent while reducing avoidable scheduling failure.
- 49 words maximum. What acceptance scenario best tests the boundary between laboratory and service operations?
This mandate is confidential. The client is named only under a mutual NDA, and your own record is never listed, sold or shown to a company under your name until you release it for this specific mandate.