LevCore by Truegyre

Answers in force.

LevCore is one governed core per hospital. Each reviewed answer is tied to the exact source version it was approved against, and is withdrawn inside LevCore when that source changes, with signed, checkable evidence.

Built and tested internally on synthetic material, being validated now.

The problem

When the policy changes, who stops the old answer?

Policies, procedures and records change. The answers people already copied, saved and repeated do not. Accreditors and auditors ask a hard question: can you show that obsolete guidance was withdrawn, and when?

LevCore makes withdrawal part of the answer itself. An approved answer is bound to the source version it came from, so when that source changes, the answer comes down.

Built today

How a reviewed answer works.

Built and tested internally on synthetic documents. Search uses keyword matching today, and every answer is written and approved by a person: no AI generation.

  1. Approve

    A reviewer approves an answer against an exact version of a source document.

  2. Serve

    People search the sources they are permitted to see, and get the approved answer with the exact version it came from. Every request is checked against their current access.

  3. Change

    The source document is replaced or withdrawn in LevCore.

  4. Withdraw

    The approved answer is withdrawn inside LevCore, with signed, checkable evidence of what was served, to whom, and when it came down.

  5. Recheck from other tools

    Other software agents can find an approved answer, fetch it, and check that it is still valid before they use it.

The LevCore Hospital Hub

One governed core per hospital, with modules around it.

The hub runs on-premise in the hospital, on an annual subscription per hospital. It includes PulseEdge and Synapse. Modules switch on only when they are ready for that site.

Built

Institutional Guidance

Approved answers for policies, SOPs and accreditation evidence, each bound to its exact source version and withdrawn on change.

In development

Evidence Validity

Tracks the evidence behind everything LevCore serves, and marks an output stale, hidden or no longer the latest when its evidence or the person's access changes.

In development

Document Intelligence

Brings scanned and stored documents in with page, version and source kept, and text read from scans reviewed before it is used.

In development

Clinical Intelligence

Patient-scoped evidence retrieval: finds the relevant record or scanned page for a clinician to review, and shows exactly where it came from.

In development

Learning (reviewed)

Local terms and templates added only with reviewer approval, each with its source and scope, checked before use and reversible.

In development

Add-on modules

A documentation-gap review workflow and a separate coder workbench, both for professional review and sign-off.

Later

Domain packs beyond healthcare

The core is domain-neutral, so the same governed evidence can serve banks and financial institutions, government and enterprise. Planned for later.

In development

Also in development

Semantic search, live connectors to document management systems, text recognition for scanned records at scale, and AI assistance for specific tasks, released only after each is qualified.

Where it runs

Inside your boundary, under your access rules.

Patient data stays within your hospital-controlled boundary.LevCore runs on-premise, one hub per hospital.
Your patients' records are never used to train a model.A fixed rule of the design, not a setting.
Each reviewed answer carries signed, checkable evidence.Who approved it, against which source version, and when it was withdrawn.

Intended use and limits

What LevCore is for, and what it isn't.

  • Documentation help, evidence retrieval and review, and completeness checks for professional review.
  • Human-reviewed answers with the exact source version shown.
  • No diagnosis, treatment recommendations or autonomous coding.
  • LevCore does not decide which revision of a document is legally in force, and does not withdraw content held in other systems.
  • Not yet qualified for clinical use, and holds no certification. Modules marked in development are not available today.

Watch an old answer come down.

A LevCore briefing walks through one policy change on synthetic documents: the approved answer, the source change, and the withdrawal with its evidence.

Request a LevCore briefing