Illustrative scenario: During a prenatal visit, a patient tells you privately that her partner pushed her, then asks you not to write it down because he checks her portal. Two instincts can both cause harm: leaving out clinically relevant information, or putting a detailed disclosure and safety plan in a broadly visible note. The OB/GYN task is to document care accurately while checking who may see the information and what privacy protections the practice can actually provide.
Start with the visibility map
Before discussing what will go in the chart, explain confidentiality and its limits, including any reporting duties that may apply under local law. Do not promise that a portal note is private. Ask the patient—while alone—what forms of contact and documentation feel safe.
Check more than whether a partner has formal proxy access. A partner may know the patient’s password, use a device that stays logged in, or see messages on a shared phone. Ask whether it is safe to leave voicemail, send texts, or use the portal, and whether the patient wants to review what will be documented.
| Record surface | Why to check it | Ask or verify |
|---|---|---|
| Note, diagnosis, and problem list | These may be visible in the portal or to other members of the care team. | What access does the partner have, and can the relevant encounter or note be restricted under clinic policy? |
| After-visit summary, results, and messages | Information may be printed, released automatically, or sent to a shared account or device. | What can appear automatically, and which communication channel is safe? |
| Billing and insurance communications | An explanation of benefits may reach the policyholder through a process outside the clinician’s control. | Who receives insurance communications, and can the billing or privacy team explain available options? |
| Linked maternal-newborn or other records | Sensitive information may be copied or auto-populated into another record, where a different person may have proxy access. | Could this information flow into a linked chart, and who can access that chart? |
A patient may be alone in the examination room without controlling who can see an app or a printed summary afterward. In obstetric care, notes and follow-up move across prenatal visits, triage, delivery, and postpartum care; some information may also flow into linked records. Keeping relevant history available for safe care matters, but so does avoiding accidental disclosure. An explanation of benefits is a separate pathway from the clinic’s portal, so do not imply that an EHR setting controls it.
Keep the record useful, not exhaustive
When documenting a disclosure, separate what the patient reports from what you observe. Attribute the account clearly—for example, record that the patient states her partner pushed her—and use her own words when a direct quote conveys an important detail. Describe observed injuries precisely, including location, size, appearance, and tenderness when assessed. Do not turn the note into a conclusion about credibility or claim to determine who caused an injury.
A body map or photograph can help document findings, but neither is required for every disclosure. Ask for informed consent before photographing, follow institutional procedures for secure storage, and respect a refusal. A patient’s disclosure does not itself establish that a particular injury is visible, and the absence of an observed injury does not disprove what she reports.
A concise, clinically relevant record can support continuity when another obstetric clinician later needs to understand an injury, a care decision, or a follow-up plan. At the same time, details such as a safe location, a shelter’s contact information, an advocate’s contact details, or the specifics of an escape plan can create risk if placed in a broadly accessible field. Avoid putting those details in an ordinarily accessible note unless needed for care; follow institutional policy for protected documentation and discuss the approach with the patient and the appropriate IPV or privacy team.
Use privacy controls only when you have checked them
Know whether your EHR can restrict an encounter or note, prevent a specific item from appearing in the portal, or change proxy access—and what each setting actually affects. A confidential flag may not suppress every diagnosis, result, after-visit summary, linked record, or downstream copy. If the workflow is unclear, consult the designated privacy or health-IT team and follow institutional policy and applicable law. Do not promise that information is hidden until the relevant access path has been verified.
Changing portal credentials or removing a proxy may help in some situations, but first ask whether making that change could itself draw attention or increase risk. Agree on a safe communication plan before sending referrals, appointment reminders, or resource information. Do not falsify a diagnosis or create a misleading note. Document clinically relevant care accurately, limit unnecessary sensitive details, and use approved privacy processes or protected documentation pathways where appropriate.
A brief conversation can make the process collaborative:
We can talk through what I would record, why it matters for your care, and who may be able to see it. I want to check what privacy options this clinic can actually use and what kind of follow-up is safe for you. I can’t promise a note is invisible to everyone, so let’s plan together.
Avoid the two documentation extremes
Writing nothing can leave later clinicians without information needed for continuity. Writing every detail into a standard, easily shared note can expose the patient or someone helping her. The aim is not a perfect note that serves every possible future purpose; it is an accurate, proportionate record made with the patient’s safety, care needs, and information access in view.
Remember that local reporting requirements vary. Explain the limits of confidentiality rather than promising either absolute secrecy or automatic police notification. If there is an immediate safety concern, address it directly and involve the appropriate clinical and support teams while preserving the patient’s autonomy wherever possible.
Practical takeaways
- Ask privately who can access the portal, devices, messages, insurance communications, and any linked records before documenting sensitive details.
- Explain confidentiality limits and discuss what will be recorded, how it may be shared, and why it is relevant to care.
- Separate the patient’s account from observed findings; use objective descriptions rather than judgment or legal conclusions.
- Photos and body maps are options, not prerequisites; obtain consent for photographs and follow secure-storage procedures.
- Avoid unnecessary safety-plan and advocate contact details in broadly accessible fields.
- Use only privacy controls you have verified, and do not promise that a note is hidden or create inaccurate documentation to conceal it.