Practice EHR
- Prenatal flowsheet and problem list
- Estimated due date with its dating history
- Visit notes and orders
OB-GYN
OB-GYN software development
A pregnancy produces months of visits, scans and labs in the clinic, and then has to reach labor and delivery complete and on time. Agnotic Technologies builds OB-GYN software that keeps one prenatal record, hands it to the hospital and follows every gynecology result back to the patient.
Prenatal flowsheetUltrasound structured reportsAntepartum handoffCLIA result tracking
Trusted by global innovators
What is OB-GYN software?
OB-GYN software is the clinical system an obstetrics and gynecology practice uses to keep a prenatal record across visits, file ultrasound reports, send the antepartum summary to labor and delivery, link mother and newborn records and track in-office gynecology labs. Agnotic Technologies builds OB-GYN software for practices and women's health service lines, connected to the EHR.
The prenatal record runs longer than most clinic charts. The estimated due date, gestational age, problem list and flowsheet carry from the first visit to delivery, and the dating can change when an early scan refines it.
This page covers the clinic's own clinical and reporting workflows. Patient pregnancy apps, population maternal risk programs and gynecologic cancer care each have their own page, linked at the end.
Decision table
Which record does each pregnancy stage create, and how does it move?
The table we map an OB-GYN build from. Interfaces depend on what each system supports, so we confirm them during scoping.
| Pregnancy stage | Record it creates | System that owns it | Interface used |
|---|---|---|---|
| First prenatal visit | History, estimated due date, initial labs and the start of the prenatal flowsheet | Practice EHR | HL7 FHIR R4 Condition and Observation for the record; HL7 v2 orders and ORU results for labs |
| Routine prenatal visits | Flowsheet rows for weight, blood pressure, fundal height and fetal heart rate, plus screening results | Practice EHR | HL7 v2 ORU or FHIR Observation for results from the reference lab |
| Ultrasound | Images and the OB-GYN ultrasound report with fetal biometry | Ultrasound system and PACS, with the report filed to the EHR | DICOM images and DICOM SR using TID 5000, OB-GYN Ultrasound Procedure Report |
| High-risk referral | Referral, consult note and shared care plan with maternal fetal medicine | Practice EHR and the specialist's system | Referral and consult documents, or FHIR ServiceRequest where supported |
| Labor and delivery | Antepartum summary available at hospital admission | Hospital EHR receives it | IHE Antepartum Summary (APS) document, or FHIR documents where the hospital accepts them |
| Birth and postpartum | Delivery details, newborn record linked to the mother, birth data for vital records and the postpartum visit | Hospital EHR and the jurisdiction's vital records office | HL7 FHIR BFDR for birth and fetal death reporting |
Birth reporting to vital records is done by the delivering facility under each jurisdiction's rules; the clinic's part is making sure the antepartum data behind it is complete.
Connected systems
Which systems feed the prenatal record?
Five sources, one record. Each keeps owning its data, and the prenatal view reads from all of them.
Ultrasound and PACS
- Images stored in PACS
- Structured measurements from the ultrasound system
- Signed report filed to the chart
Reference and in-office labs
- Orders and results over HL7 v2
- Waived tests run in the office
- Abnormal results routed to the clinician
Hospital labor and delivery
- Antepartum summary before admission
- Delivery outcome back to the clinic
- Newborn record linked to the mother
Patient channels
- Visit reminders that follow gestational age
- Pre-visit questions
- Messages to the care team
Failure points
Where do OB-GYN workflows break?
Problems we design around on every OB-GYN build.
Challenge
The due date changes after an early scan, but the old date stays on forms.
Agnotic approach
Dating is one field with a history, and every form and the flowsheet read the current date and show how it was set.
Challenge
Ultrasound reports arrive as PDFs with no measurements.
Agnotic approach
Structured reports are read from the ultrasound system, so biometry lands as discrete values the flowsheet can trend.
Challenge
Labor and delivery cannot see the prenatal record at admission.
Agnotic approach
The antepartum summary goes to the delivering hospital from a week the practice chooses, and is sent again after each later visit.
Challenge
Pap and HPV results come back and nobody follows up.
Agnotic approach
Every gynecology result opens a follow-up task that stays open until the patient is told and the next step is booked.
Challenge
The newborn is a new patient with no link to the mother.
Agnotic approach
Mother and newborn records are linked at delivery, so the postpartum visit and the baby's first visits share the history they need.
Gynecology labs
How should in-office gynecology labs be tracked?
Practices that test specimens in the office hold a CLIA certificate for those tests. The software keeps testing inside that certificate and ties every result to a follow-up.
- Each in-office test mapped to the CLIA certificate it runs under
- Waived tests, such as visual urine pregnancy tests, recorded with kit lot and expiry
- Send-out Pap and HPV tests ordered over HL7 v2, with results matched back to the order
- Abnormal results routed to the clinician with a due date for patient contact
- A report of orders with no result and results with no follow-up
- Quality control records kept beside patient results
What do we build into OB-GYN software?
Modules for the obstetric and gynecology sides of the practice.
Prenatal flowsheet
Weight, blood pressure, fundal height, fetal heart rate and screenings visit by visit on one timeline with gestational age.
Ultrasound integration
DICOM structured reports and images from the ultrasound system and PACS, with biometry stored as discrete values.
Antepartum summary to labor and delivery
The prenatal record sent to the delivering hospital before admission and refreshed after later visits.
Gynecology lab tracking
In-office and send-out results matched to orders, with abnormal results tracked until the patient is contacted.
Mother and newborn linking
Delivery outcome and newborn identifiers linked to the mother's record for postpartum care.
Scheduling and reminders
Visit schedules that follow gestational age, with reminders and pre-visit questions for patients.
Codes and standards
Which codes and standards does OB-GYN software use?
HL7 FHIR R4HL7 FHIR BFDRIHE APSDICOM SR TID 5000HL7 v2 ORUICD-10-CM chapter 1542 CFR Part 493
Facts and sources
Standards and rules behind OB-GYN software
Short facts from HL7, IHE, DICOM and CLIA, each linked to its primary source.
The HL7 FHIR Birth and Fetal Death Reporting (BFDR) implementation guide, STU2, defines Composition and Bundle profiles for birth and fetal death reporting, with content based on the 2003 revisions of the U.S. Standard Certificate of Live Birth and the U.S. Standard Report of Fetal Death; data about the mother can be sent separately from the labor and delivery encounter data.
Source: HL7 FHIR Birth and Fetal Death Reporting IG (HL7)The IHE Antepartum Summary (APS) profile starts from the need for obstetric patients admitted to Labor and Delivery to have a complete summary of their antepartum ambulatory care at admission, drawn from the initial history and physical, office visits, laboratory and ultrasound studies and serial exams such as fundal height and fetal heart rate.
Source: IHE PCC Antepartum Summary (APS) profile (IHE)DICOM PS3.16 template TID 5000, OB-GYN Ultrasound Procedure Report, is the root template for OB-GYN ultrasound structured reports and includes sections for fetal biometry, fetal long bones, fetal cranium, the biophysical profile, the fetal anatomy survey and early gestation.
Source: DICOM PS3.16, TID 5000 OB-GYN Ultrasound Procedure Report (NEMA)A laboratory is out of compliance with CLIA unless it holds a current certificate of waiver, registration certificate, certificate of compliance, certificate for provider-performed microscopy procedures or certificate of accreditation that covers the examinations it performs, or is CLIA-exempt.
Source: 42 CFR 493.3(a) (eCFR)A laboratory can qualify for a CLIA certificate of waiver only if it limits its testing to the waived tests listed in the regulation, which include visual color comparison urine pregnancy tests, or tests added to that list later.
Source: 42 CFR 493.15(c) (eCFR)
Compliance-First Healthcare App Development Services Backed by Global Standards
01
HIPAA
Health Insurance Portability and Accountability Act
Protect PHI with privacy-first architecture, encrypted storage and transmission, strict access controls, and traceable audit logs.
02
GDPR
General Data Protection Regulation
Implement lawful consent flows, data minimization, retention controls, and secure processing for sensitive health data.
03
FHIR
Fast Healthcare Interoperability Resources
Enable standardized health data exchange across apps, care teams, and systems through standards-based FHIR APIs.
04
HL7
Health Level Seven International
Support enterprise-grade interoperability with HL7-based integrations for records, events, and clinical messaging workflows.
05
HITRUST
Health Information Trust Alliance
Align security programs to healthcare-specific control and risk management practices trusted by providers and ecosystem partners.
06
HITECH
Health Information Technology for Economic and Clinical Health Act
Design with breach notification readiness, digital record safeguards, and operational controls that support regulated care programs.
07
SaMD
FDA Software as a Medical Device
Plan software quality, traceability, and documentation pathways for products that may require SaMD review and submission.
08
MDR (EU)
Medical Device Regulation (European Union)
Prepare EU market-ready processes for risk classification, evidence tracking, and lifecycle governance under MDR expectations.
09
SAMHSA
Substance Abuse and Mental Health Services Administration
Apply confidentiality controls and consent-aware sharing models for behavioral and mental health data experiences.
Who it is for
Who do we build OB-GYN software for?
Teams that need the prenatal and gynecology record to work across the clinic and the hospital.
OB-GYN practices
Single and multi-site practices that need a prenatal record and result tracking their general EHR does not give them.
Women's health service lines
Health system service lines connecting clinics, ultrasound and labor and delivery.
Maternal fetal medicine groups
Specialist practices that take referrals and share care plans with the referring obstetrician.
Health tech founders
Startups building prenatal, ultrasound or women's health clinic products who need HIPAA-ready engineering.
Engagement
How does an OB-GYN software engagement work?
We map one pregnancy end to end before we build.
1.
Scoping call
We walk through one pregnancy from first visit to postpartum with your clinicians, sonographers and front desk.
Scope2.
Fixed-scope first release
The prenatal flowsheet, ultrasound report import and result tracking for one site, with weekly demos.
Build3.
Scale and support
The antepartum summary to your delivering hospitals, more sites and patient reminders, with support after launch.
ScaleScope and cost
What drives the cost of OB-GYN software?
We do not publish prices. These are the things that change the size of a build, and we price them on the scoping call.
EHR and hospital connections
What your practice EHR and each delivering hospital expose for reading and sending records.
Ultrasound systems
How many ultrasound machines and PACS, and whether they send structured reports.
Labs
Reference labs for orders and results, and the waived tests you run in the office.
Scope of the record
Prenatal care only, or gynecology result tracking and postpartum care as well.
Patient channels
Reminders and pre-visit questions by text, email or an existing patient app.
Data migration
Open pregnancies and result history carried over from the current system.
Frequently Asked Questions
Yes. Most builds sit beside the practice EHR and read and write through its FHIR R4 and HL7 v2 interfaces, adding the prenatal and result tracking views the EHR lacks. We confirm what your EHR exposes during scoping.
From DICOM structured reports. The OB-GYN ultrasound report template carries fetal biometry and other measurements as coded values, so we file them as discrete results rather than a scanned PDF.
We send an antepartum summary, following the IHE Antepartum Summary profile or the hospital's preferred format, ahead of the due date and again after later visits.
Birth and fetal death reporting is done by the delivering facility to the jurisdiction's vital records office. For hospital clients we build it with the HL7 FHIR BFDR implementation guide; for clinics we make the antepartum data it relies on complete.
Yes. Each result opens a follow-up task, abnormal results go to the clinician, and a report lists any result where the patient has not been contacted or the next step is not booked.
A laboratory testing patient specimens needs the CLIA certificate that matches the tests it performs, even when it runs only waived tests. The software records which tests run under your certificate, and your laboratory director confirms the certificate type.
No. This is the clinic's clinical system. Consumer pregnancy apps for education and tracking are a separate product on our pregnancy app page, and they can connect to the clinic record when you want them to.