Extract data from progress notes

Every clinical encounter leaves a progress note, and its four-part SOAP shape is the closest thing medicine has to a universal record across US inpatient and outpatient charts: Subjective is what the patient reports, Objective is what the clinician measured, Assessment is the working impression, and Plan is what happens next. LOINC files the document itself under code 11506-3, but the note behind that code is typed or dictated into an EHR by hundreds of clinicians who each phrase it their own way. A hospitalist rounding on an inpatient, a nurse charting a vitals block, and a coder abstracting the encounter for billing each read the same note for different fields: the temperature of 38.4 C and blood pressure of 148/92, the medications reviewed or started, the assessment with its ICD-10 diagnoses, and the plan with its follow-up and procedures. The difficulty is that the four sections blur together on the page. Vitals get buried mid-sentence in the objective narrative, an assessment lists three diagnoses at different statuses, and a plan folds a medication change, a lab order, and a two-week follow-up into one paragraph. Amended and addended notes carry a status that changes what counts as current. A note documented 2026-06-11 by Dr. Selin Yavuz at Riverside General Hospital, patient born 1969-02-08, needs the vitals lifted into a typed block, the medications split into an array with dose instructions, and the diagnoses tied to ICD-10 codes, so the encounter reaches the chart and the coding queue as structured JSON rather than a scanned PDF page. Because a progress note is PHI, it stays inside the platform rather than going to a general model.

What gets extracted from progress notes

How extraction works for progress notes

Progress notes come out of inpatient EHR systems, outpatient charting tools, and dictation that lands as a scanned PDF, and the SOAP sections rarely sit in tidy blocks. Talonic classifies the note and maps it to the clinical-document model in the Field Registry, which pulls the subjective, objective, assessment, and plan apart, lifts the vitals into a typed block, and returns medications, observations, procedures, and ICD-10 diagnoses as their own arrays. LOINC-coded observations keep their code and value, the note status of final, amended, or addended is captured so a superseded version is not read as current, and the managing organization, provider credentials, and NPI are read where shown. Every field carries a confidence score and a pixel-region pointer conforming to DIN SPEC 91491, so a coder at a US hospital can verify a diagnosis or a blood pressure against the source note. Talonic structures the note and does not diagnose, code, or infer anything the clinician did not write.

Sample extraction

A one-page outpatient follow-up progress note in SOAP format

{
  "document_date": "2026-06-11",
  "patient.name": "Diego Fuentes",
  "patient.medical_record_number": "8830145",
  "patient.date_of_birth": "1969-02-08",
  "provider.name": "Dr. Selin Yavuz",
  "provider.credentials": "MD",
  "status": "final",
  "subjective": "Two days of worsening dyspnea on exertion, mild ankle edema",
  "objective": "Bibasilar crackles; no acute distress",
  "vital_signs.temperature": 38.4,
  "vital_signs.blood_pressure": "148/92",
  "vital_signs.heart_rate": 96,
  "vital_signs.respiratory_rate": 20,
  "assessment": "CHF exacerbation",
  "plan": "Increase furosemide to 40 mg BID; BMP in 1 week; follow-up 2026-06-25",
  "diagnoses": [
    {
      "diagnosis_code": "I50.9",
      "diagnosis_description": "Heart failure, unspecified"
    }
  ]
}

Frequently asked