Reference implementation · Clinical records
A visit, checked before the note.
Built as GammaLexCare to prove the layer on clinical records. Prior visits, care plans, patient-reported changes, and provider decisions are assembled for the visit happening now, and the run reports what is missing, changed, conflicting, or out of bounds before anything is drafted.
How the layer worksWhat one visit depends on.
Starting from today's visit, the run follows the chart out to prior visits, plans, and decisions — and stops where the onset was never recorded.
Records, and what links them
- Where the run starts
- Followed, and used
- Should exist. Does not.
- Relevant, and not permitted
What carries in, and what the run reports.
Select a point in the history to see what it left behind and what the run returns before the note is final.
GammaLexCare · Visit context
Request
Document today's visit.
What came before
What it carries forward
- Live conversationCaptured in the room, linked back to what was said.
- Everything aboveCarried in, so the visit does not restart from zero.
Before the note is final
- NOT FOUND
Onset was never recorded
The symptom has been discussed twice without an onset. It is still askable while the patient is in the room.
- STALE
The plan moved since the last note
A medication was started after the earlier plan was written, so that plan no longer describes current care.
- CONTRADICTORY
Two records describe the symptom differently
What the patient reported between visits does not match what was documented at the last one. Both are surfaced.
- RESTRICTED
A record outside this patient
A similar record from another chart was held at the boundary and kept out of this visit.
Nothing is finalized until a clinician approves it — and what they approve becomes context for the next run.
The same layer, on your records.
GammaLex supplies the context infrastructure. Partners own the workflow and the interface.
The patent implementation