rmerk ↗ analysis ↗ GitHub rmerk/mike
rmerk is rebuilding Mike into a Minnesota-anchored medical-malpractice records engine for med-mal reviewers.
This fork takes Mike in a sharply vertical direction: a records-review platform for Minnesota medical-malpractice work. rmerk is layering jurisdiction-specific structure onto the base product - chronology timelines, clinical lenses for medications and vitals, and a compliance gate tied to Minnesota's §145.64 peer-review rule - so that reviewers can move through a patient's chart the way a med-mal attorney actually reads it.
rmerk is also reshaping the engine room. The default AI brain has shifted away from Google toward Kimi K2.6 via NVIDIA's model catalog, opening a fourth provider slot in the process. Smaller quality-of-life work - a memory-leak fix in the document viewer, orientation notes for coding agents - suggests someone who is living in this codebase day to day, not just prototyping.
If you're a Minnesota med-mal reviewer or you build tools for one, this is the fork worth clicking through on. Everything else here is in service of that audience.
What's in it
- Minnesota med-mal records platform A five-phase build turning Mike into a jurisdiction-specific records-review tool, anchored to Minnesota statutes and case law.
- Chronology timeline view A fast, citation-anchored medical history that turns the underlying event log into a navigable patient timeline - no AI call required to render it.
- MAR and Vitals clinical lenses Pivot a flat chart into medication-administration or vitals views, so reviewers can read the chronology the way clinicians actually structure it.
- §145.64 peer-review compliance gate Peer-review material is filtered out of med-mal extraction across both typed text and scanned pages, with no opt-out.
- NVIDIA model catalog with Kimi K2.6 default A fourth AI provider slot is wired in, and the out-of-the-box model is Kimi rather than Google's.
- DocView stability fix A memory leak in the document viewer was tracked down and closed - small, but the kind of fix that signals someone is actually using this for long review sessions.
Direction
discoverycomplianceworkflow
Activity
rmerk ↗ analysis ↗ GitHub rmerk ↗ analysis ↗ GitHub rmerk ↗ analysis ↗ GitHub Threads of work (detailed view)
rmerk turns Mike into a Minnesota med-mal records engine
A jurisdiction-specific product layer for medical-malpractice case review, anchored to Minnesota statutes and case law at every step.
rmerk adds NVIDIA's model catalog and makes Kimi the default
A fourth AI engine slot opens up in this fork, and the out-of-the-box brain is no longer Google's.
rmerk gives med-mal records a real chronology view
A new Timeline turns an existing event log into a fast, citation-anchored medical history - no AI call required.
rmerk closes the peer-review loophole in med-mal extraction
A compliance gate that only read typed text now reads the scans too - and there is no off switch.
rmerk splits the medical timeline into clinical lenses
Med-mal reviewers on the fork can now pivot a patient's chart into medication-administration and vitals views instead of one flat chronology.
Pull requests (detailed view)
🟢 Open (1)
rmerk · opened 15d ago ✅ Merged (3)
rmerk · opened 15d ago · merged 15d ago by rmerk rmerk · opened 15d ago · merged 15d ago by rmerk rmerk · opened 16d ago · merged 16d ago by rmerk ⛔ Closed without merge (1)
rmerk · opened 16d ago · closed 16d ago