Obstetrics is the clearest case in ambulatory medicine for a record organised around an episode.

The RealityOne episode, forty weeks, one sheet

⚠️

The Problem

Twelve visits, twelve islands.

Each encounter documented on its own, so seeing a trend means opening several notes and holding numbers in your head while you do it.

🔧

The Solution

One flowsheet, computed gestational age.

A single continuous view across the pregnancy, with gestational age derived from an established dating method rather than typed at each visit.

✅

The Resolution

A trend a clinician can read in seconds.

Values line up by week, screening results sit where they are needed, and the handoff at delivery carries what the next clinician needs.

The visit schedule is the spine of the build

Design the flowsheet around the cadence and most of the layout decides itself. Columns by visit, rows by measurement, ordered so the things that trend sit together and the things checked once sit apart.

The cadence also tells you where the density changes. Monthly visits early, fortnightly through the third trimester, weekly at the end — a flowsheet built with even column widths wastes space early and crowds exactly where the clinical attention concentrates.

Two timed items anchor the middle of the record. NICHD describes gestational diabetes screening between 24 and 28 weeks and a pertussis booster between 27 and 36 weeks. Both are windows rather than dates, which makes them a natural fit for a computed prompt rather than a task somebody remembers.

Gestational age should be computed, never typed

This is the single highest-value configuration decision in the build, and it is frequently left as free text.

Gestational age at any point is a function of an established due date and the current date. Establish it once — from the last menstrual period, reconciled against dating ultrasound — store the basis, and let every subsequent display derive from it. Typed gestational age drifts, contradicts itself between notes, and is impossible to report on.

Store the method as well as the date. “40 weeks by LMP” and “40 weeks by 8-week ultrasound” are different claims with different confidence, and a later clinician reading the record deserves to know which one they are looking at.

Risk screening and where the results have to live

The first visit carries an unusually heavy documentation load. NICHD’s description of it runs to more than twenty items, covering history, family and genetic history, lifestyle, physical and pelvic examination, and a block of laboratory work including blood type and Rh factor, blood count, hepatitis B, HIV, rubella and syphilis.

Most of that is captured once and referenced for the rest of the pregnancy, which has a specific implication: those results need to be visible from the flowsheet rather than buried in the first encounter. A clinician at week thirty should not have to go back to week eight to find an Rh status.

The practical pattern is a header band on the flowsheet holding the once-established facts — dating, blood type and Rh, significant history, screening results — above the columns that repeat. It costs a little screen space and removes a whole category of navigation.

Structured capture: pick the rows that matter

The repeating rows are where the flowsheet earns its keep, and the list is shorter than most builds make it.

Blood pressure, weight, fundal height, fetal heart rate, urine findings, presentation and oedema cover what NICHD describes as the substance of a later visit. Seven rows. Everything else — the conversation, the concerns raised, the plan — is narrative and belongs in the note rather than in a grid pretending to be data.

Practices that try to structure the narrative end up with a flowsheet nobody completes fully, which is worse than a smaller one completed reliably. This is the same lesson that applies to every specialty flowsheet, and it is worth settling during template development rather than after go-live, usually alongside the wider visit workflow.

The postpartum handoff, and why it is the weak point

The prenatal record is built by one team and needed by another. Delivery frequently happens somewhere the practice does not control, postpartum care may return to the practice or not, and the information that has to cross that boundary is not always the information that crosses it.

This matters more than a records problem usually does. HRSA states that pregnancy-related mortality has not improved over the past decade and that four out of five pregnancy-related deaths are considered preventable, figures it attributes to underlying federal and non-federal sources. It also reports that thirty-five percent of US counties lack hospitals or birth centres offering obstetric care, with about sixty percent of those in rural counties — which means the handoff is often to a team at a distance.

Design for that. The handoff document should be generated from the flowsheet rather than retyped, it should carry the risk factors and the screening results rather than a summary of them, and somebody should own confirming it arrived.

What the surveillance data asks of the record

There is a reporting dimension worth knowing about even if your practice does not participate directly.

CDC’s Pregnancy Risk Assessment Monitoring System draws a stratified sample from birth certificate files and surveys new mothers, with mailings beginning two to four months after delivery and topics covering preconception, prenatal and postpartum care, obstetric history, substance use, physical abuse, contraception, economic status, maternal stressors and early infant health.

The relevance to a flowsheet build is indirect but real: the domains that get surveyed are the domains that get measured, and a record that captures them as data rather than as prose is a record that can answer questions about its own population.

• Compute gestational age from a stored dating method. Never a typed field.
• Put once-established facts in a header band. Rh status should not need archaeology.
• Keep repeating rows to about seven. Narrative belongs in the note.
• Generate the handoff from the flowsheet. And name who confirms it arrived.

Qventive works as a prenatal flowsheet EHR company would, though the work usually sits inside our OB/GYN EHR and IT support and a broader OB/GYN practice management engagement rather than being sold as a form.

Because the prenatal record moves between organisations at delivery, the exchange belongs in your HIPAA risk analysis alongside the clinical design, and remote check-ins between visits are worth scoping with your telehealth setup rather than separately.

Prenatal records: common questions