Lyrax
Book a walkthrough

Every patientready before they arrive.

For hospitals, clinics and IVF centres. The paperwork arrives already done, every AI suggestion says why, and a clinician signs before anything reaches a chart.

Book a walkthroughTour it with fictional data

The clinic, the front desk and the patient's phone all read one record, and the safety rules are enforced under it, not on the screen.

  • Built around HIPAA obligations
  • Second factor enforced in the database
  • Row-level security on every table
  • Append-only audit log
Watch one visit come together

Before the visit — step 1 of 5

Nobody retypes the referral.

History, medications and coverage arrive from the record exchange and fill the chart themselves. Duplicates are folded on the way in, and every field says where it came from.

Intake · new patientAssembled
Referral
Dr. Osei · cardiology consultFax
History
HTN · T2DM · smoker, quit 2019HIE
Medications
Metformin 500 mg · Lisinopril 10 mgHIE
Coverage
Cascade Mutual PPO · verifiedPayor

Two sources sent the same medication. Kept once, both cited.

An illustrative visit. Every name in it is fictional.

As the record lands — step 2 of 5

Every risk flag says why.

A readiness score appears as the record loads, with the findings that produced it listed underneath. You can disagree with it, because you can see what it read.

Readiness riskModerate
  • HbA1c 8.1%Lab · Tuesday
  • On anticoagulantMedication list
  • Prior reaction to contrastNotes, 2024

Every band shows the data that drove it: a flag you can argue with.

At the point of signature — step 3 of 5

The wrong drug doesn't get signed.

Prescribe against a recorded allergy and the signature is refused until a reason is entered. The rule sits in the database, so no screen can skip it.

New prescription

Amoxicillin 500 mg · three times daily

Allergy: penicillinsame family as the recorded allergy
Refused
  • A reason, recorded
  • The allergy list shown, attached to the override

A database rule, not a popup. Checked again at the bedside, logged either way.

On their phone — step 4 of 5

The patient gets three things to do.

A short list in their own language, ticking itself off as they confirm. You see what they've read, and it escalates when nobody answers.

Before Thursday
  • Nothing to eat after midnight
  • Pause metformin 48 hours before
  • Confirm your ride home
YES

Seen · yesterday 6:12 pm

Across the group — step 5 of 5

Every site on one screen.

Sorted by which patients are ready, not by which building they're in. The screen looks the same with one practice on it or twenty-three.

Group board · 23 sitessorted by readiness, not by building
  • Site 01
  • Site 02
  • Site 03
  • Site 04
  • Site 05
  • Site 06
  • Site 07
  • Site 08
  • Site 09
  • Site 10
  • Site 11
  • Site 12
  • Site 13
  • Site 14
  • Site 15
  • Site 16
  • Site 17
  • Site 18
  • Site 19
  • Site 20
  • Site 21
  • Site 22
  • Site 23

The board keeps its shape from one practice to twenty-plus. Illustrative sites shown.

Every step above is signed and logged.

Who did it, when, and what they were looking at. It is a better record than paper, kept without anybody stopping to keep it.

Signed.

Book a walkthroughTour it with fictional data

Built for how you are organised.

Treatment cycles, end to end

Stimulation monitored every other day, the trigger decision, retrieval, the embryology lab, cryostore, transfer and outcome, with the double-witnessing and consent trail the lab is held to.

Open the doctor workspaceIn IVF clinic mode. Management and patient are a click away inside.
  • ManagementCycle outcomes by age band, lab and cryo capacity
  • DoctorThe cycle board, scan day, the embryology lab
  • PatientWhere I am, what I inject tonight, when I find out

Already built, not on a roadmap.

24 modules in the product today

The chart

  • Problem listcoded, with an onset and a status; a problem is resolved, never deleted
  • Allergiesthe reaction, the severity and how sure anybody is, not just a word
  • Visitsevery note, order, result and charge hangs off the encounter it happened at
  • Order entrylabs, imaging and procedures, with the turnaround and the coverage shown first
  • Notesdrafted, signed, countersigned, and amended by addendum rather than rewritten
  • Prescribingthe sig, the quantity, the days' supply and why it was started
  • Immunisationsgiven here, reported, or from a registry, and the record says which
  • Documentsthe file itself, in private storage, not an index entry pointing nowhere

On the ward

  • Bed boardlive ward view with NEWS2 early-warning scores
  • Medication roundseMAR with barcode verification at the bedside
  • The allergy hard stopconflicting drugs refused in the database itself
  • Shift handoverSBAR, and no one can accept their own handover
  • On-call rotawho is on tonight, and the escalation ladder
  • Surgical safety checklistrefused until every required item is confirmed

Fertility

  • IVF cycle boardstimulation to transfer, embryology lab, cryostore
  • OHSS risk scoringfrom the oestradiol and follicle data already collected

Through the day

  • Schedulingday, week, month, drag-and-drop, per-doctor colours
  • Labs and imagingordered, tracked, resulted, charted
  • Billing and claimsclaim status beside the visit it belongs to
  • Discharge to portalsummaries reach the patient once published
  • Command paletteany patient, page, or action from one keystroke

Oversight

  • AI review queueevery suggestion waits for a physician's sign-off
  • Audit and access reviewappend-only log of every touch of a record
  • Privacy requestspatient data requests handled inside the product

The fastest way to judge any of them is on your own worklist.

Book a walkthroughTour it with fictional data

One record, and everything a visit leaves in it.

Three workspaces, one chart underneath them, and one log of every touch of it. Nothing below is a category or a roadmap item. Each is a table, with the columns named beside it.

  • Clinical workspaceWorklist, orders, clearance
  • ReceptionBooking and the queue
  • Patient portalSteps, visits, results
Lyrax

One record per patient, one log of everything done to it.

  • Chart
  • Intake
  • Risk
  • Orders
  • Instructions
  • Audit

Held in the record

  • ProblemsCodedOnset, status, and the date one was resolved rather than deleted
  • AllergiesStructuredSubstance, reaction, severity, and who verified it
  • VisitsEncountersOpened and closed, and closed by a named person
  • OrdersCPOEEntered against the visit, priced as they were placed
  • NotesSignedCosigned and amended; an addendum is a new entry, never an edit
  • MedicationsPrescriptionsSig, quantity, days supply, and why a course was stopped

The whole chart comes out as a FHIR R4 bundle whenever you ask for it, patient by patient: problems, allergies, visits, orders, medications, immunisations, results, notes and documents.

Patient data handled like it matters, because it does.

Encrypted

In transit and at rest

Row-level security

Enforced on every table

Append-only audit trail

Every access, logged

Second factor, in the database

Not only at the sign-in screen

Built around HIPAA obligations: multi-factor sign-in per clinic policy, idle sessions signed out, and patient consent checked before AI ever runs.

Working in it this week, not this quarter.

Four steps, and every one of them is a screen you can be shown before you decide anything. The order matters; the calendar mostly does not.

  1. Minutes

    Paste the staff list you already keep

    Select the rows in your spreadsheet, copy, paste. Names, emails, a role each. It shows you what it read before it creates anything, and the invitations go out on the same click.

  2. The same day

    Everyone joins in two steps

    Open the mail, set a password, confirm your name. Nothing to install, no workstation to visit, no client to configure and no VPN. It is a browser, including the one already in their pocket.

  3. Already done

    The access rules are written

    Pick one of forty-two roles per person. What each can reach is enforced by the database on every read and every write, so there is no permissions matrix to design in a workshop before anybody can sign in.

  4. One pass, then live

    Your patient list comes over, and charts start

    Export the list from wherever you keep it and load the file: it reads the column names however they are spelled, tells you which rows it will refuse and why, and asks which way round the dates are when the file cannot say. After that, registering somebody or accepting a referral creates the chart. No freeze on what you run today, no weekend cutover, no month of double entry.

What a rollout here does not contain

  • No migration weekend, and no freeze on the system you run today
  • Nothing to install on a workstation, and nothing to keep updated
  • No permissions matrix to design before the first person signs in
  • No gate on the demo; it is open before you have spoken to anyone

The part that is not fast

Bringing the HISTORY across from a system you already run. The patient list itself imports from a spreadsheet in one pass, and you see every row it will refuse before anything is written, but what was written in those charts is another matter, and it either comes over as documents or stays where it is. For a practice starting fresh that is nothing; for a group with years behind it, it is the decision worth having early, and it is a decision, not a project you have to finish before anybody can work.

The questions every care team asks.

Your staff are working in it the day you paste the list: invitations out, a two-step join, and roles that are already written. Patients arrive as they are registered or referred, so there is no migration weekend and no freeze on what you run today. The long pole is whatever you decide to bring across from an existing system, and that is a decision rather than a project.

It's the record. Coded problem lists, allergies with the reaction and the severity, visits, orders, notes that are signed and amended rather than overwritten, medications with the sig, immunisations, documents with the actual files, and results somebody has signed off. It also runs the shift around that record: the ward board, the drug round, handover, the cycle, the front desk and the patient's own portal. If you already run Epic or Oracle Health, it is built to exchange with them rather than argue with them.

Clinicians, coordinators and administrators get full workspaces. Patients reach their own visits, steps and results through the portal, which is not a seat.

It's designed for coordination billed as a covered medical service, and your team sees claim status inside the product, beside the visit it belongs to.

See it run against your own worklist.

Bring one site and one month of visits. We will show you where readiness is leaking and what it is worth to close it.

  • What the walkthrough covers
  • Your own flow, replayedOne month of your visits run through intake, risk, orders, and clearance in Lyrax.
  • The leak, pricedWhere slots are slipping in your numbers, and what closing the gap is worth per site.
  • The integration pathHow it connects to your EHR, and what your team keeps using completely unchanged.

Not ready to talk to anyone?

Open the live demo

Book a walkthrough

Three things to type, two to pick. No demo gate, no sales sequence.

We reply within one business day.
No patient data, ever, in this form.