Medical Record Summarizer – SOAP Note Generation

1. Overview

This process converts a single patient’s electronic health record (EHR) for a specific visit into a well‑structured SOAP note that clinicians can use directly in patient care. The EHR content is read, the essential information is extracted, and the data is organized into the four standard SOAP sections: Subjective, Objective, Assessment, and Plan.

2. Business Value

• Improves clinician efficiency – clinicians receive a ready‑to‑use note, reducing documentation time.

• Standardizes documentation – ensures every note follows a consistent format, supporting quality‑control and compliance.

• Reduces errors – automatically pulls data from the EHR, minimizing manual transcription mistakes.

• Supports billing and compliance – structured SOAP notes satisfy audit and reimbursement requirements.

3. Operational Context

4. Inputs

4.1 EHR Encounter Document (PDF)

Type: PDF document containing the full electronic health record for a single patient encounter.

Details Provided:

• Patient identifiers – full name, date of birth, medical record number (MRN).

• Encounter details – date and time of the visit, location, and encounter type (e.g., office visit, telehealth).

• Clinician information – name and professional title of the provider who performed the encounter.

• Chief complaint / reason for visit.

• History of present illness (including relevant past medical, surgical, and social history).

• Review of systems (if documented).

• Physical exam findings – vitals, general appearance, and organ‑system examinations.

• Laboratory results, imaging reports, and other diagnostic findings.

• Assessment – diagnostic conclusions or differential diagnoses.

• Plan – recommendations, prescriptions, follow‑up instructions, referrals.

Only one PDF document is required per execution of the SOP. The document must be legible and machine‑readable (i.e., not a scanned image that cannot be processed).

4.2 Optional Clinician Signature (Plain Text)

Type: Plain‑text block (optional) containing the clinician’s name and credentials as they should appear at the end of the SOAP note.

Details Provided:

• Clinician Name – e.g., “Dr. Emily Nguyen, MD”.

• Title – e.g., “Family Medicine”.

If the clinician’s name and title are already present in the EHR document, this optional input can be omitted.

5. Outputs

5.1 SOAP Note (Plain Text)

Name/Label: SOAP Note – plain‑text document.

Contents:

• Header – patient name, date of birth, encounter date, clinician name and title.

• Subjective – bullet‑point summary of chief complaint, history of present illness, and any review of systems.

• Objective – bullet‑point list of vital signs, physical exam findings, and relevant diagnostic results.

• Assessment – concise diagnostic statement(s) or differential diagnosis, each on a separate line.

• Plan – bullet‑point list of treatment orders, medication prescriptions, follow‑up appointments, referrals, patient education, and any pending tests.

Formatting Rules:

1. Header – each item on its own line, e.g., “Patient: John Doe”.

2. Section headings – full words “Subjective”, “Objective”, “Assessment”, and “Plan” each on its own line.

3. Bullet points – use a hyphen (-) followed by a space for each item.

4. Line spacing – a blank line separates each major section.

5. No extra identifiers – do not generate new IDs or reference system numbers not already in the source document.

The output is a plain‑text block ready for insertion into the patient’s chart.

6. Detailed Plan & Execution Steps

1. Open the EHR PDF and confirm it is for a single patient encounter.

2. Identify and extract the patient header information: name, DOB, MRN, encounter date, and clinician name/title.

3. Read the Chief Complaint and History of Present Illness; place this information under Subjective.

4. Collect Review of Systems (if present) and include as bullet points under Subjective.

5. Extract vital signs, physical‑exam findings, and any laboratory or imaging results. List these under Objective.

6. Locate the provider’s assessment (diagnoses, differential). Place each diagnosis on its own line under Assessment.

7. Extract the plan: medications, dosage, route, frequency, follow‑up schedule, referrals, patient‑education items, and any pending orders. List each item under Plan.

8. If a Clinician Signature input was supplied, add it to the end of the note; otherwise, use the clinician name from the EHR.

9. Compose the SOAP Note using the formatting rules defined in Section 5.1. Ensure each section heading appears on its own line, followed by bullet points.

10. Perform a final review: confirm all four sections are present, patient identifiers are correct, and no unrelated content is included.

11. Output the completed SOAP note as plain‑text.

7. Validation & Quality Checks

• Presence check – Confirm that the note contains all four sections (Subjective, Objective, Assessment, Plan).

• Header completeness – Verify patient name, DOB, encounter date, and clinician name appear in the header.

• Data accuracy – Cross‑check that every piece of information in the SOAP note appears in the source PDF. No information should be invented.

• Formatting check – Ensure each section heading is correctly spelled and capitalized, and bullet points start with “-”.

• Missing data flag – If any required field (e.g., patient name, encounter date) is missing, flag the entire note for manual review and do not generate output.

• Duplicate check – Ensure no duplicate items appear within a single section.

• Confidentiality check – Confirm that only patient‑specific data is present; no extraneous patient identifiers (e.g., staff IDs) are included.

If any validation step fails, the process stops, an error message is generated, and the case is marked for manual review.

8. Special Rules / Edge Cases

• Missing patient name or MRN – Do not proceed; flag for manual review.

• Multiple patients in a single PDF – Abort processing and flag for manual review.

• Scanned image that cannot be parsed – Flag as “Unreadable Document” and request a readable version.

• Absent laboratory results – Add “No laboratory results provided.” under Objective.

• No plan items – Insert “No specific plan documented.” under Plan.

• Clinician name not found – Use “Clinician: Not provided” in the header and flag the note for review.

• Encounter date missing – Flag for review; do not generate output.

9. Example

Input (EHR Document – PDF) – represented here in plain text for illustration

• Patient Name: John Doe

• Date of Birth: 01/15/1975

• Medical Record #: 12345678

• Date of Encounter: 08/10/2025

• Clinician: Dr. Emily Nguyen, MD – Family Medicine

Chief Complaint: “Chest pain that started this morning.”

History of Present Illness:

• Onset 3 hours ago, sharp, 5/10 intensity, worsens with deep breath.

• No shortness of breath, no nausea.

Review of Systems:

• Cardiovascular: No palpitations, no edema.

Physical Exam:

• Vitals: BP 130/80, HR 88, RR 16, Temp 98.6°F, SpO₂ 97% on room air.

• Cardiac: Regular rate and rhythm, no murmurs.

• Lungs: Clear to auscultation bilaterally.

Labs:

• Troponin: 0.01 ng/mL (normal).

Assessment:

• Likely musculoskeletal chest pain (costochondritis).

Plan:

• Prescribe ibuprofen 400 mg PO q6h PRN for pain.

• Recommend warm compresses and rest.

• Follow‑up in 2 weeks or sooner if symptoms worsen.

Output (SOAP Note – plain text)

Patient: John Doe
Date of Birth: 01/15/1975
Date of Encounter: 08/10/2025
Clinician: Dr. Emily Nguyen, MD – Family Medicine

Subjective
- Chief complaint: Chest pain started this morning, 5/10, sharp, worsens with deep breath.
- History of present illness: Onset 3 hours ago, no shortness of breath, no nausea.
- Review of systems: Cardiovascular – no palpitations, no edema.

Objective
- Vitals: BP 130/80, HR 88, RR 16, Temp 98.6°F, SpO₂ 97% on room air.
- Physical exam: Cardiac – regular rate and rhythm, no murmurs; Lungs – clear to auscultation bilaterally.
- Labs: Troponin 0.01 ng/mL (within normal limits).

Assessment
- Musculoskeletal chest pain (likely costochondritis).

Plan
- Ibuprofen 400 mg PO every 6 hours as needed for pain.
- Warm compresses and rest.
- Follow‑up in 2 weeks or sooner if symptoms worsen.

Appendix A – FAQ

Q1: What if the EHR document does not include a Review of Systems? A1: Omit the Review of Systems portion from the Subjective section. The note remains valid.

Q2: How should I handle a lab result that is pending? A2: List “Pending – ” under Objective.

Q3: The patient’s date of birth is missing from the EHR. What should I do? A3: Do not proceed with note generation. Flag the case for manual review.

Q4: What format should the final note be delivered in? A4: As plain‑text, using the formatting rules in Section 5.1. No PDF, CSV, or other file types are produced.

Q5: The PDF contains a scanned image that cannot be parsed. A5: Mark the document as “Unreadable – scanned image.” Request a machine‑readable version before proceeding.

Q6: Should I include any patient identifiers other than the ones listed? A6: No. Use only the patient’s name, date of birth, and medical record number as provided. No additional IDs should be added.

Q7: How do I indicate a missing or “not provided” field? A7: Insert “Not provided.” under the relevant section.

Q8: The physician’s name is not in the EHR. What should I write in the header? A8: Write “Clinician: Not provided” and flag the note for manual review.

Appendix B – Glossary

Appendix C – Reference Materials

C.1 SOAP Note Structure Guide

1. Header

• Patient: <Full name>

• Date of Birth: <MM/DD/YYYY>

• Date of Encounter: <MM/DD/YYYY>

• Clinician: <Name>, <Degree>, <Specialty>

2. Subjective

• Chief complaint: <patient’s words or summary>

• History of present illness (HPI):

  • - <key point 1>

  • - <key point 2> …

• Review of Systems (optional):

  • - <system> – <positive/negative>

3. Objective

• Vitals: BP <value>, HR <value>, RR <value>, Temp <value>, SpO₂ <value>

• Physical examination:

  • - <system> – <findings>

• Lab / imaging results:

  • - <test name>: <result> (<reference range>)

4. Assessment

• <Diagnosis or impression>

• <Differential diagnosis> (optional)

5. Plan

• Medication: - <drug> <dose> <frequency> for <indication>

• Procedures / Tests: - <test> scheduled for <date>

• Follow‑up: - <time frame>

• Patient education: - <instructions>

• Referral: - <specialist>, <date>

C.2 Formatting Rules

1. Headings – use exact words “Subjective”, “Objective”, “Assessment”, “Plan”.

2. Bullets – use a hyphen and a single space (“- ”) before each item.

3. Spacing – one blank line between each major section; no extra blank lines inside a section.

4. Capitalization – first word of each bullet is capitalized; rest of the bullet follows normal sentence case.

5. Numerical data – use numeric values and abbreviations (e.g., “BP 120/80”).

C.3 Prohibited Content

• No generation of new identifiers such as system‑generated IDs, order numbers, or random codes.

• No external references – do not include URLs, external guidelines, or citation links.

• No personal opinions – the note must remain factual and clinically relevant.

C.4 Common Pitfalls & How to Avoid Them

C.5 Example of a Complete SOAP Note (Reference)

Patient: Jane Smith
Date of Birth: 03/22/1989
Date of Encounter: 09/01/2025
Clinician: Dr. Michael Lee, MD – Internal Medicine

Subjective
- Chief complaint: Persistent cough for 2 weeks.
- History of present illness: Dry cough, worse at night; no fever or chest pain.
- Review of systems: Respiratory – no shortness of breath; GI – normal appetite.

Objective
- Vitals: BP 122/78, HR 72, RR 14, Temp 98.2°F, SpO₂ 98% on room air.
- Physical exam: Lungs clear bilaterally; no wheezes.
- Labs: CBC normal, chest X‑ray normal.

Assessment
- Upper respiratory infection (viral).
- No evidence of pneumonia.

Plan
- Symptomatic treatment: Guaifenesin 600 mg PO q6h PRN for cough.
- Advise increased fluid intake and rest.
- Follow-up in 5 days or earlier if symptoms worsen.

Additional Notes

• Maintain patient confidentiality at all times. The SOAP note should only be shared with authorized clinical staff.

• If any step of the process is unclear, consult the FAQ or Glossary before proceeding.