Who uses CliniNote
Three workflows where unstructured notes become the bottleneck
Real-world evidence teams, patient recruitment coordinators, and outcomes researchers all face the same wall: ICD codes cover about 40% of what matters. The rest is locked in clinical narrative. CliniNote unlocks it.
Real-world evidence
Build RWE datasets that hold up to scientific scrutiny
Regulatory-grade real-world evidence requires more than claims data. Investigators need diagnosis confirmation, treatment details, and outcome events documented in clinical narrative, not just coded in a billing field that may lag by weeks.
CliniNote extracts ICD-10 diagnoses with confidence scores, retrieves medication records from progress notes where pharmacy claims don't reflect inpatient administration, and pulls lab values and procedure dates documented only in physician summaries.
Each output row carries a source citation tied to the originating note, sentence, and character offset. Auditors can trace any data point back to the text that generated it, supporting the documentation standard that submission reviewers expect.
Patient eligibility screening
Find eligible patients before manual review, not after
Trial eligibility criteria reference diagnoses, prior medications, lab thresholds, and procedure history. Most of this information exists only in notes. Screening coordinators who rely on structured fields alone miss patients who would qualify, and waste time on patients who don't.
Upload your eligibility criteria as a structured phenotype definition. CliniNote maps each criterion to the relevant entity types, runs extraction across your note corpus, and returns a ranked list of candidate patients with the supporting evidence for each criterion.
The result: coordinators spend their time on clinical judgment calls, not on opening charts to check whether a diagnosis mentioned in a note two years ago is actually an exclusion criterion.
Outcomes research
Measure outcomes that billing codes never see
Rehospitalization within 30 days. Symptom resolution. Treatment escalation. Adverse events noted by the attending. These endpoints live in narrative, and CliniNote puts them into your analysis dataset.
Outcomes researchers building retrospective cohorts face a familiar problem: the outcome they care about is documented as a note entry, not as a discrete coded event. A readmission for heart failure decompensation may appear in the discharge summary before the ICD code is assigned. A medication discontinuation due to side effects appears in the progress note, not in the pharmacy record.
CliniNote supports custom event extraction: define the clinical outcome in natural-language terms, and the system returns timestamped event candidates with the source note, the extracted entity, and the confidence score. Your team validates the flagged candidates, not the 90% that don't match the outcome definition.
The structured output integrates directly with statistical environments. Export the event dataset as a CSV with patient identifiers, event dates, event types, and confidence scores for time-to-event analysis, propensity matching, and other standard outcomes methods.
Every extracted event carries the source citation, so your statistician's table and the clinical note that drove it remain traceable throughout the analysis and into any submission package.
Which workflow fits your team?
Tell us about your study or screening challenge. We will walk you through how CliniNote would handle it with a sample of your data.