One platform. Every provider. Every pathway. Every patient. Compliance Agent Navigates legal landscape by state, country, insurer, and pathway before any treatment decision. Journey Generation Personalized step-by-step treatment plan with clear milestones, cost estimates, and decision points. Cost Engine Real-time out-of-pocket transparency across all providers and payers. Provider Matching Network, budget, proximity, and appointment booking across the full care ecosystem. Personal AI Concierge Personal care orchestration agent providing guidance and engagement throughout the journey. For accuracy: all five agents are currently coded as conditional logic (if/else) — a structured foundation that maps the decision tree before intelligence is layered on top. Once synthetic and real data testing is complete, we will begin training the agentic versions. The Compliance Agent is the exception — it is already in active development as a true AI agent.

A FHIR-native, interoperability-first architecture being built on open standards, AI agents, and enterprise-grade security. Architecture Overview Micro services based, cloud-native. Event-driven orchestration layer being built to connect patient-facing apps, clinical systems, payer APIs, and AI agents through a unified data bus. Designed for deployment on Docker/Kubernetes with multi-region support. Interoperability & FHIR Mapping Designed to be FHIR R4 compliant across all data exchanges. SMART on FHIR integration planned for EHR app launch. Resources mapped: Patient, Observation, Condition, CarePlan, Claim, Coverage, Practitioner, Appointment, Medication Request. Bidirectional sync planned with clinic Electronic Health Records and payer systems. InterSystems IRIS Integration Core interoperability and data platform — native FHIR R4 server, high-performance data management, and production-grade integration engine. IRIS Interoperability is planned to orchestrate HL7 v2, FHIR, and REST message routing. Security & Compliance Design in progress for HIPAA compliance. GDPR-ready architecture in progress for international deployments. OAuth 2.0 + SMART authorization. AES-256 encryption at rest, TLS 1.3 in transit. Role-based access control (RBAC). Audit logging planned on all PHI access. AI & ML Frameworks Design in Progress for Knowledge Graph: Neo4j + IRIS semantic layer. LLM orchestration: LangChain + custom fine-tuned models in development on reproductive health corpus. Multi-agent architecture with tool-calling and memory planned. Knowledge Graph Backbone Symptoms → Diagnostics → Diagnosis → Provider Specialty → Care Protocol → Itemized Steps → Costs. Built on SNOMED CT, LOINC, CPT, ICD-10. Planned to power journey generation, provider matching, and cost engine. Being built to become the reference architecture for reproductive health — open, interoperable, and enterprise-ready.

A separate Technical Deep Dive document is available upon request — covering architecture diagrams, API specs, FHIR mapping, InterSystems IRIS integration, data flow documentation, security & compliance design, deployment model, auth model, rate limits, endpoints list, and frameworks. RESTful API Endpoints Versioned REST APIs (v1/v2) for all platform functions — journey generation, cost engine, provider matching, compliance rules, and concierge actions. OpenAPI 3.0 spec published for partner integrations. Auth Model OAuth 2.0 with PKCE for patient-facing apps. SMART-on-FHIR for EHR-launched contexts. API key + JWT for B2B integrations (clinics, payers, employers). Token refresh with sliding expiry. Rate Limits & SLAs Standard tier: 1,000 req/min per client. Clinical tier: 5,000 req/min with priority queuing. 99.9% uptime SLA. Webhook support for real-time event notifications (appointment changes, lab results, plan updates). Data Flow Inbound: EHR → FHIR Adapter → Normalized Patient Model → Knowledge Graph. Outbound: AI Agent decisions → Care Plan updates → EHR write-back + patient app + payer notification. All flows logged and auditable. IRIS FHIR Server & Repository IRIS Health FHIR R4 server hosts the canonical patient record. All FHIR resources persisted, versioned, and queryable. Supports $everything operation for full patient record retrieval at point of care. IRIS Integration Engine IRIS Interoperability (formerly Ensemble) orchestrates HL7 v2, FHIR, and REST message routing between clinic EHRs, labs, pharmacies, and payer systems. Business rules engine handles transformation, routing, and error handling. Deployment Model Cloud-native (AWS). Containerized microservices via Kubernetes. IRIS deployed as managed cloud instance. Patient app: React Native (iOS/Android). Clinician portal: React web app. Monitoring & Observability Distributed tracing (OpenTelemetry). Centralized logging (ELK stack). Real-time dashboards for API health, agent performance, and care coordination metrics. Alerting on PHI access anomalies. Being built to be the reference architecture for reproductive health — open, interoperable, and enterprise-ready.

Provider & Patient Interfaces Emotional wellness and physical wellness modules. Appointment booking and medical history screens. Labs, imaging, diagnosis, procedures and surgeries features. Provider-facing and patient-facing dashboards. Workflow Logic & FHIR Interoperability Core workflow orchestration layer. FHIR R4 API integration with InterSystems IRIS. SMART-on-FHIR authentication. Knowledge Graph & Journey Visibility Open-source reproductive healthcare knowledge graph: Symptoms → Diagnostics → Diagnosis → Provider Specialty → Care Protocol → Itemised Steps → Costs. Powers journey generation, provider matching, and cost engine from a single semantic layer. Pilot Readiness: What We Plan to Test Built on the three completed work streams — Provider & Patient Interfaces, Workflow Logic & FHIR Interoperability, and Knowledge Graph & Journey Visibility — the platform now enters structured testing and pilot launch. Synthetic Data Testing Validate all platform logic, FHIR mappings, agent behaviour, and workflow orchestration using synthetic patient datasets. Stress-test edge cases across fertility, adoption, and GP referral pathways. Real Data Testing Controlled testing with consented real-world data from pilot clinic partners. Validate knowledge graph accuracy, journey generation quality, provider matching precision, and cost engine reliability. HIPAA Compliance & Pilot Launch Complete HIPAA compliance review and GDPR-readiness audit. Finalise security architecture (OAuth 2.0, AES-256, TLS 1.3, RBAC, audit logging). Launch pilot with first cohort of fertility clinic and GP partners.

Building the connective tissue between fertility clinics, GPs, EHRs, payers, and adoption networks — through open standards and enterprise-grade integration. Phase 2: Planned (Stage 1) Q3 2026 FHIR R4 Core Integration FHIR R4 API layer built on InterSystems IRIS for Health. Core resources mapped: Patient, Observation, Condition, CarePlan, Claim, Coverage, Practitioner, Appointment, MedicationRequest. SMART-on-FHIR authentication in progress. EHR Connectivity Bidirectional sync planned with clinic EHRs (Epic and partner systems). HL7 v2 message routing via IRIS Interoperability. Labcorp and diagnostic system integration in progress. GP Referral & Care Coordination GP-to-clinic referral logic being built. Care coordination workflows connecting primary care entry points to ART providers and adoption networks. EDI claims integration planned. Non-Medical Provider Connectivity Architecture designed to connect adoption agencies, counselling services, and support networks alongside fertility clinics — enabling a full parenthood pathway, not just a clinical one. Phase 2 · Test & Pilot (Stage 2) Q4 2026 Synthetic Data Testing Validate FHIR mappings, EHR connectivity, and GP referral logic using synthetic patient datasets across fertility and adoption pathways. Real Data Testing & Pilot Controlled testing with consented real-world data. Validate interoperability accuracy across all connected providers. Launch pilot with first cohort of fertility clinic and GP partners.

Phase 3 · Planned (Stage 1) Q3 2026 B2C Provider Matching Interface Medical and non-medical provider matching interface. Care pathway visibility with access management and patient consent. Appointment and referral management. Employer Portal (B2C-Dependent) An employer-facing interface built on top of the B2C patient platform. Enables employers to offer fertility and parenthood benefits — covering IVF, adoption support, and counselling — as part of employee health packages. Dependent on B2C patient journey dashboard being live first. Planned for integration once B2C milestone is met. Patient Journey Dashboard Patient journey dashboard with milestone tracking, cost transparency, and mobile-first design (WCAG 2.1 accessible), powered by the knowledge graph. Phase 3 · Test & Pilot (Stage 2) Q4 2026 Real Data Testing Controlled testing with consented real-world data from pilot clinic partners. Validate knowledge graph accuracy, journey generation quality, provider matching precision, and cost engine reliability. HIPAA Compliance & Pilot Launch Complete HIPAA compliance review and GDPR-readiness audit. Finalise security architecture (OAuth 2.0, AES-256, TLS 1.3, RBAC, audit logging). Launch pilot with first cohort of fertility clinic and GP partners. Workstreams 4–7 (Compliance Agent, Cost Engine, Journey Generation Agent, Provider Matching Agent & Personal AI Concierge) continue in parallel and will be integrated progressively as milestones are met.

Primary Care Patient ART Clinic Patient Insurer Member Employer Talent State Constituent Our solution is designed to sit at the intersection of all five relationships — coordinating care, benefits, and navigation in one unified platform.

Emotional Health version can be leveraged across multiple diseases. The agentic, FHIR-native infrastructure and decentralised AI orchestration framework — is redeployable across any longitudinal, multi-provider public health challenge where fragmentation, dropout, and coordination failure are the core problems. Emotional & Mental Health Fragmented pathways between GPs, psychiatrists, therapists, and crisis services mirror fertility's coordination failure. PtP's compliance agent, journey generation, and AI concierge can orchestrate longitudinal mental health journeys — reducing dropout, managing medication adherence, and connecting patients across the full care continuum. Substance Abuse & Recovery Recovery journeys span detox, rehabilitation, peer support, housing, and employment — with no shared data and no coordinating layer. The same agentic architecture can track milestones, surface the right intervention at the right moment, and maintain continuity across providers and jurisdictions. Obesity & Metabolic Health Effective obesity care requires coordinated input from GPs, dietitians, endocrinologists, behavioural therapists, and pharmacists. PtP's provider matching, cost engine, and journey generation can power personalised, multi-disciplinary weight management pathways — including GLP-1 protocol management and long-term adherence tracking. Chronic Disease Management Conditions like diabetes, hypertension, and COPD demand the same longitudinal, multi-provider coordination that PtP is building for fertility. The knowledge graph backbone and IRIS integration layer are directly transferable to any chronic condition pathway. Women's Health Beyond Fertility Menopause, endometriosis, PCOS, and postpartum mental health are all underserved, fragmented, and ripe for the same orchestration model — particularly in contexts where PtP is already building relationships. One architecture. Many crises. The fertility pilot providing inclusive access to is the target proof of concept.

The central insight driving strategy is straightforward: primary care already knows the patient. GPs hold longitudinal records, manage comorbidities, and are trusted by patients. They must become the active link between patient need and ART provision. This model transforms GPs from passive bystanders into active care coordinators — reducing wasted cycles, improving patient readiness, and giving commissioners the data they need to demonstrate value.

Every cycle wasted on an ineligible or insufficiently prepared patient represents a direct cost to the healthcare system and a failed opportunity for a family. By intervening at each of these three failure points, Partners to Parenthood demonstrably improves the ratio of funded cycles to live birth outcomes — the metric commissioners, clinicians, and patients all share.

Patient Dashboard

PROVIDER CLINICAL Hub shows vitals, labs, imaging, diagnoses, medications, wellness, documents, and history. From here the care team can open any record or add new results.

PROVIDER CLINICAL DATA: LABS The provider records lab results directly in the application choosing the test, value, and source. The same simple form is reused to capture a full panel of results as they come in.

PROVIDER CLINICAL DATA: LABS

PROVIDER CLINICAL DATA: IMAGING MEASUREMENT

PROVIDER CLINICAL DATA: IMAGING IMAGINING Hydrosalpinx Finding PtP notes the implications for treatment.