A basal FSH result of 10 IU/L is a piece of information. By itself, it sits within a broadly normal range for most laboratories. What it does not tell you is whether this is the patient's first early follicular phase measurement, whether it represents an increase from a consistent 7 IU/L over the previous two years, whether it was drawn on cycle day 3 as intended or on cycle day 5 due to a scheduling issue, or how it sits alongside the patient's AMH level and antral follicle count from the same cycle. The number is real, but the number in isolation is substantially less informative than the number in context.
This is not a controversial observation for anyone who works in fertility medicine. What is worth examining is why the systems most clinics use to store this data actively work against the contextual reading that experienced clinicians rely on.
The architecture of disconnection
Hormone assay results in a fertility clinic typically arrive through one of two pathways: a direct feed from the laboratory's information system (LIS) into the clinic's EMR, or a manual entry from a printed or emailed lab report. Either way, the result lands in a lab results module that is structurally separate from the cycle record.
The cycle record is maintained in a different part of the system, usually a spreadsheet or a dedicated cycle tracking module. The cycle day on which a blood draw occurred may be recorded in the cycle log and nowhere in the lab results module. The lab result may carry a calendar date but no cycle day reference. These two facts, existing in the same software installation and describing the same patient on the same day, cannot be read together without manual reconstruction.
The same pattern applies to imaging. A day-10 monitoring scan in a stimulated cycle is meaningful in direct relation to the follicle growth rate that the preceding scans and oestradiol levels suggest. When the scan report and the hormone results are stored in separate locations with no structural link between them, reading them together requires a clinician to hold both in memory simultaneously, which is exactly the kind of cognitive load that increases with consultation volume and time pressure.
What cycle-day anchoring adds
Positioning a hormone result on a cycle-day timeline rather than a calendar date changes what the result communicates. A cycle day 2 FSH draw is a basal measurement; a cycle day 9 FSH draw in the context of an antagonist protocol is a stimulation response indicator; an FSH result without cycle day context is harder to read than it should be for anyone who was not the clinician who ordered the draw.
For a patient returning for her third stimulated cycle, the clinician's reading of the current cycle's day 2 FSH is informed by the day 2 FSH values from the previous two cycles and the stimulation responses those cycles produced. If those historical values are available at a glance, aligned on a single timeline with the current cycle, the reading is efficient. If the clinician must retrieve them from two previous consultation notes or a historical lab printout, the same information takes considerably longer to assemble.
We are not claiming that having contextual data changes clinical outcomes. That is a claim for clinical research to evaluate. What we can observe, from conversations with fertility nurses and consultants in our early-access group, is that the time required to assemble contextual data before a consultation is a consistent friction point, and that the friction compounds across a morning session with multiple patients.
AMH as a case study in context dependency
Anti-Mullerian Hormone (AMH) is relatively stable across a menstrual cycle compared to FSH, which is why some protocols use it as a preferred ovarian reserve marker. However, AMH is not cycle-day independent in all contexts. In patients undergoing hormonal suppression, values may differ from baseline. In patients who have recently undergone ovarian surgery, values may reflect changes in ovarian reserve rather than a stable baseline.
A single AMH value, taken once at a point in a patient's clinical history, is informative about ovarian reserve at that time. A series of AMH values across eighteen months, viewed alongside the patient's cycle history and any relevant interventions, tells a more complete story about how reserve has changed over the treatment period. That longitudinal view is only available if the values are stored in a system that presents them together rather than as discrete, date-stamped entries in a results list.
This is the specific kind of context dependency that a patient timeline addresses: not simply having the data, but having it in a format where the temporal and clinical relationships between values are visible.
The practical argument for integration
The case for integrating cycle data and hormone results on a single timeline is not primarily a data completeness argument. Most clinics already have this data; the problem is that it is stored in a way that makes combining it more difficult than it needs to be.
It is also not primarily a technology argument. The data types involved are well-understood, the relevant standards for health data exchange (HL7 FHIR, SNOMED CT for coded lab values) are established, and the technical barriers to integration are lower than the clinical adoption barriers.
The practical argument is simpler: when cycle context and lab results can be read together in the same view, the clinician's preparation time for a consultation decreases. The reading work that previously required cross-referencing two systems becomes a single screen task. The contextual inference that the clinician was doing manually, by holding multiple values in memory and comparing them, is supported by the visual structure of the data.
We are not saying integrated data replaces clinical judgement. The clinician still interprets the context; the system simply makes the context visible. What changes is how much time the reading takes and how many individual acts of recall and cross-reference are required to do it. For a clinician preparing for twelve patients in a morning, that difference adds up.
What the integration does not do
To be explicit: combining cycle data and hormone lab results on a timeline does not produce a recommendation. Amilis does not flag values as concerning, does not suggest protocol adjustments, and does not score a patient's response. Those judgements require clinical expertise and a complete picture of the patient's circumstances that no data platform fully holds.
What the timeline provides is visibility. The clinician who sees an FSH trend, positioned on cycle days, across three treatment cycles and alongside the patient's imaging history is in a better position to apply their clinical judgement than one who is reconstructing the same picture from separate sources under time pressure. Better data visibility is the goal; clinical decision-making remains the clinician's task entirely.