High-Risk & MFM
When MFM, your office and the hospital share a pregnancy, the patient calls one of you at random. How co-management calls get sorted to the right owner.
A co-managed high-risk pregnancy usually involves your office, an MFM service and a delivery hospital, and the patient has no reliable way to know which of the three owns a given question. She rings the number she has, and whoever answers improvises a transfer. Writing the ownership rules down once removes that guesswork from every call.
Being told to ring the other office is not a resolution, it is a second call the patient may or may not make. Capturing the question fully on first contact means that even when the answer lives elsewhere, your practice hands over something complete rather than sending her away to start again.
Glucose readings, home blood pressures, kick counts: these arrive as values the patient wants recorded, and a paraphrased message loses them entirely. Structured capture puts the readings, the times and the context into the handoff, without the system offering any view on any of them.
Every co-management relationship is negotiated locally and no two look the same. Your practice writes which conditions and question types belong to whom, and the system applies that split identically day and night, with a log of what was routed where and when.
24/7 coverage
Co-managed patients reach a live answer overnight, when the MFM office is closed
Condition and weeks captured
Gestational age and the stated high-risk condition recorded before any routing
Your ownership rules, executed
The split between your practice, MFM and the hospital applied the same way on every call
No, it applies the split your practice wrote. You define which conditions, question types and gestational ages belong to your office, to the co-managing service, or to the hospital. The system forms no clinical judgement about who is best placed to answer.
They are captured as stated, with the values and the times they were taken, and routed on your rules. The system does not evaluate whether a reading is high, low or concerning, and it never tells a patient that a number is acceptable.
Not to the routing. The destination can be an external phone number, a shared inbox, a fax workflow or a structured summary your staff forwards. This is available through secure workflow automation where no direct interface exists between the two organisations.
Those follow the branch your practice authored, which for most obstetric practices points at existing triage instructions rather than at any scheduling path. The system asks your questions and routes; it does not assess, grade or reassure.
Yes. The call establishes who is currently managing the pregnancy and flags any mismatch with what your record shows, so your staff can reconcile it rather than discovering it at the next visit.
A structured handoff: identifiers, gestational age, the stated condition, the question with any values given, callback number, the branch taken and timestamps. Delivery into an EMR task queue is available through API or FHIR for supported systems.
Related
Prenatal Visit Cadence and Recall Scheduling
The visit schedule that gets denser and more divided once a pregnancy becomes co-managed.
Related
Obstetric Calls That Must Go to Labor and Delivery
The standing instruction that overrides co-management routing when the answer is the hospital's.
Related
Prenatal Screening Result Calls in Obstetrics
The result that most often creates a co-managed pregnancy in the first place.
Pillar guide
AI Receptionist for OB/GYN Practices
The full OB/GYN phone workflow: obstetric triage, gynecologic clinic calls, results, surgery and after-hours coverage.
See how MedReception AI handles after-hours calls, scheduling, intake, and patient communication for medical practices like yours.
